← previous blocknext block →recent activity
Analyzing
Block #84,289,886
10 transactions · 9 stateful · 2026-06-28 17:05:02 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,289,886 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfefd1e1d…5fed
0x34b655…2a6f
4 touches
1 conflict
0x18978822…2623
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe99d8e68…a16e
0x34b655…2a6f
4 touches
1 conflict
0x0833f1ab…71e7
0x34b655…2a6f
2 touches
0 conflicts
0x13fa020b…57a3
0x34b655…2a6f
2 touches
0 conflicts
0x1e346a85…e9c5
0x34b655…2a6f
2 touches
0 conflicts
0x32229dd3…4dbb
0x34b655…2a6f
2 touches
0 conflicts
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 0xfefd1e1d05…695fed
Audit this contract →
← previous block·next block →recent activity