← previous blocknext block →recent activity
Analyzing
Block #84,563,331
22 transactions · 18 stateful · 2026-06-29 23:28:29 UTC
Parallelism
86/100
Blocked
39%
Avg conflicts / tx
0.41
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,563,331 · 22 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
1w02w113w015w116w117w118w119w220w021w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9dbefc67…4855
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x093880ac…71a5
0x34b655…2a6f
4 touches
1 conflict
0x1a3ed36a…3063
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5bdb0bbb…f5a2
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x793aa64d…b09c
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 0x9dbefc672a…064855
Audit this contract →
← previous block·next block →recent activity