← previous blocknext block →recent activity
Analyzing
Block #84,361,960
22 transactions · 19 stateful · 2026-06-29 01:05:25 UTC
Parallelism
86/100
Blocked
21%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,361,960 · 22 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w06w18w013w115w219w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xab86573c…682e
0x34b655…2a6f
4 touches
1 conflict
0xe8dff05d…7914
0x5afd3e…7620
4 touches
1 conflict
0x56d453cf…7e9a
0x5afd3e…7620
4 touches
1 conflict
0x20e120e6…5b73
0x5afd3e…7620
4 touches
1 conflict
0x1717b2de…0010
0x5afd3e…7620
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x3d472183…1138
0xd32edf…ff58
3 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
1 conflict on slot 0xab86573c9c…f3682e
Audit this contract →
← previous block·next block →recent activity