← previous blocknext block →recent activity
Analyzing
Block #84,461,495
25 transactions · 21 stateful · 2026-06-29 12:08:46 UTC
Parallelism
72/100
Blocked
43%
Avg conflicts / tx
0.64
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #84,461,495 · 25 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w08w111w212w313w415w016w117w118w220w521w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe560375e…4626
0x34b655…2a6f
8 touches
6 conflicts
0x9a5244ed…fc88
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x35de07e6…7751
0x34b655…2a6f
4 touches
1 conflict
0x3da49e5d…8067
0x34b655…2a6f
4 touches
1 conflict
0x767fd47d…67ed
0x34b655…2a6f
4 touches
1 conflict
0x826cce18…251c
0x34b655…2a6f
4 touches
1 conflict
0xb4527790…c282
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 0xe560375e1e…614626
Audit this contract →
← previous block·next block →recent activity