← previous blocknext block →recent activity
Analyzing
Block #84,075,425
11 transactions · 9 stateful · 2026-06-27 17:16:30 UTC
Parallelism
73/100
Blocked
44%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,075,425 · 11 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
1w03w04w17w18w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49194594…2c70
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x1d2a8430…30bf
0xa6afd3…d132
4 touches
1 conflict
0x2e72f452…bd7a
0x34b655…2a6f
4 touches
1 conflict
0x3de5fb8b…400a
0xa6afd3…d132
4 touches
1 conflict
0x17cc5ec3…ae0e
0x34b655…2a6f
4 touches
1 conflict
0xe138b6d2…085f
0xa6afd3…d132
3 touches
1 conflict
0x75cff376…7357
0xa6afd3…d132
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 0x4919459402…d42c70
Audit this contract →
← previous block·next block →recent activity