← previous blocknext block →recent activity
Analyzing
Block #84,365,551
20 transactions · 19 stateful · 2026-06-29 01:29:20 UTC
Parallelism
65/100
Blocked
42%
Avg conflicts / tx
0.65
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #84,365,551 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w07w08w19w210w313w115w416w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x93641233…06f5
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xbfe63d66…c3e6
0x34b655…2a6f
6 touches
3 conflicts
0xffb1ee54…7c2c
0x34b655…2a6f
6 touches
3 conflicts
0x2f4d415d…5f95
0x34b655…2a6f
6 touches
3 conflicts
0x72bbdcc6…69ae
0x34b655…2a6f
4 touches
1 conflict
0x85c2e11f…7992
0x34b655…2a6f
4 touches
1 conflict
0x97c67486…27fe
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
6 conflicts on slot 0x9364123348…4106f5
Audit this contract →
← previous block·next block →recent activity