← previous blocknext block →recent activity
Analyzing
Block #84,461,403
27 transactions · 23 stateful · 2026-06-29 12:08:09 UTC
Parallelism
81/100
Blocked
22%
Avg conflicts / tx
0.33
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,461,403 · 27 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
1w013w014w116w020w221w322w423w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7a2b18bf…d24e
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x1274880c…3cdc
0x34b655…2a6f
4 touches
1 conflict
0x13c5b486…d41e
0x34b655…2a6f
4 touches
1 conflict
0x18978822…2623
0x34b655…2a6f
4 touches
1 conflict
0x26731ffc…6b25
0x34b655…2a6f
4 touches
1 conflict
0x57be321f…fecc
0x34b655…2a6f
4 touches
1 conflict
0x581b829b…9578
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 0x7a2b18bfee…11d24e
Audit this contract →
← previous block·next block →recent activity