← previous blocknext block →recent activity
Analyzing
Block #84,024,381
18 transactions · 13 stateful · 2026-06-27 11:36:35 UTC
Parallelism
78/100
Blocked
23%
Avg conflicts / tx
0.17
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,024,381 · 18 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
5w08w116w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x157dbfb2…4089
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xb3975d93…b4a2
0x34b655…2a6f
4 touches
1 conflict
0xc9fe0433…7f01
0x34b655…2a6f
4 touches
1 conflict
0x7a2fc410…c088
0x34b655…2a6f
4 touches
1 conflict
0x5c2b9886…705b
0x34b655…2a6f
4 touches
1 conflict
0x73ca2093…8dd6
0x34b655…2a6f
3 touches
1 conflict
0x8726ff39…3be8
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 0x157dbfb216…8d4089
Audit this contract →
← previous block·next block →recent activity