← previous blocknext block →recent activity
Analyzing
Block #84,080,453
19 transactions · 14 stateful · 2026-06-27 17:50:03 UTC
Parallelism
79/100
Blocked
21%
Avg conflicts / tx
0.21
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,080,453 · 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
6w010w117w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7a2b18bf…d24e
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f1
0x34b655…2a6f
4 touches
1 conflict
0xb166aabd…9c06
0x34b655…2a6f
4 touches
1 conflict
0xbaeed020…92f8
0x34b655…2a6f
4 touches
1 conflict
0xc09c3422…3c8b
0x34b655…2a6f
4 touches
1 conflict
0xc2c97680…568f
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 0x7a2b18bfee…11d24e
Audit this contract →
← previous block·next block →recent activity