← previous blocknext block →recent activity
Analyzing
Block #84,598,010
11 transactions · 9 stateful · 2026-06-30 03:19:34 UTC
Parallelism
64/100
Blocked
33%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,598,010 · 11 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
3w04w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbc8ead31…90fd
0x34b655…2a6f
8 touches
6 conflicts
0x274b85f7…c526
0x34b655…2a6f
6 touches
3 conflicts
0x3f75fb9e…0d2e
0x34b655…2a6f
4 touches
1 conflict
0x5d7f309d…5145
0x34b655…2a6f
4 touches
1 conflict
0x5f447bf3…57c7
0x34b655…2a6f
4 touches
1 conflict
0x7fe97198…79ab
0x34b655…2a6f
4 touches
1 conflict
0x86a6e399…369e
0x34b655…2a6f
4 touches
1 conflict
0x909aac83…694a
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 0xbc8ead31d9…0790fd
Audit this contract →
← previous block·next block →recent activity