← previous blocknext block →recent activity
Analyzing
Block #84,599,656
15 transactions · 15 stateful · 2026-06-30 03:30:33 UTC
Parallelism
67/100
Blocked
27%
Avg conflicts / tx
0.73
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,599,656 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w07w011w112w213w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x742072b0…1af8
0x34b655…2a6f
6 touches
4 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
6 touches
3 conflicts
0xca3931f0…0855
0x34b655…2a6f
6 touches
3 conflicts
0x63da0619…7a55
0x34b655…2a6f
5 touches
3 conflicts
0x55b55e59…cb67
0x34b655…2a6f
4 touches
1 conflict
0x5fad6fee…7714
0x34b655…2a6f
4 touches
1 conflict
0x6a5119b4…26dc
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity