← previous blocknext block →recent activity
Analyzing
Block #84,084,500
14 transactions · 9 stateful · 2026-06-27 18:17:03 UTC
Parallelism
86/100
Blocked
22%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,084,500 · 14 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
1w02w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x157dbfb2…4089
0x34b655…2a6f
4 touches
1 conflict
0x384a61b8…664d
0x34b655…2a6f
4 touches
1 conflict
0x42341814…60f1
0x34b655…2a6f
4 touches
1 conflict
0x53371568…a089
0x34b655…2a6f
4 touches
1 conflict
0x7506443a…4820
0x34b655…2a6f
4 touches
1 conflict
0x7a2fc410…c088
0x34b655…2a6f
4 touches
1 conflict
0x925c118c…a1d8
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 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 0x157dbfb216…8d4089
Audit this contract →
← previous block·next block →recent activity