← previous blocknext block →recent activity
Analyzing
Block #84,121,773
15 transactions · 13 stateful · 2026-06-27 22:25:26 UTC
Parallelism
80/100
Blocked
23%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,121,773 · 15 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
1w02w111w012w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00966e54…7d1d
0x34b655…2a6f
6 touches
3 conflicts
0xdc8d4ee0…def3
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xbc6f10d1…20a9
0x34b655…2a6f
6 touches
3 conflicts
0x5a30d8a9…f768
0x34b655…2a6f
6 touches
3 conflicts
0x22cf8fc6…68e5
0x34b655…2a6f
6 touches
3 conflicts
0xc05b880b…7746
0xa6afd3…d132
4 touches
1 conflict
0x157dbfb2…4089
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
3 conflicts on slot 0x00966e5492…9a7d1d
Audit this contract →
← previous block·next block →recent activity