← previous blocknext block →recent activity
Analyzing
Block #84,024,437
10 transactions · 8 stateful · 2026-06-27 11:36:58 UTC
Parallelism
60/100
Blocked
38%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,024,437 · 10 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w07w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa0c6e179…a103
0x34b655…2a6f
6 touches
3 conflicts
0x73ca2093…8dd6
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xb7c66e7c…49f3
0x34b655…2a6f
4 touches
1 conflict
0x137a69a8…8b93
0x34b655…2a6f
2 touches
0 conflicts
0x326a02b5…8dad
0x34b655…2a6f
2 touches
0 conflicts
0x5d4a3441…e31c
0x34b655…2a6f
2 touches
0 conflicts
0x67fc285e…2584
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
3 conflicts on slot 0xa0c6e1796c…01a103
Audit this contract →
← previous block·next block →recent activity