← previous blocknext block →recent activity
Analyzing
Block #84,610,141
19 transactions · 16 stateful · 2026-06-30 04:40:30 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,610,141 · 19 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
1w02w15w010w215w116w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x744e0a36…70f7
0x34b655…2a6f
6 touches
3 conflicts
0x19df8d7c…4259
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x086db8fc…0024
0x34b655…2a6f
6 touches
3 conflicts
0x05ef50ec…7052
0x34b655…2a6f
4 touches
1 conflict
0x2011ff06…05aa
0x34b655…2a6f
4 touches
1 conflict
0x2965e2d6…5800
0x34b655…2a6f
4 touches
1 conflict
0x4383029f…f951
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 0x744e0a3655…6d70f7
Audit this contract →
← previous block·next block →recent activity