← previous blocknext block →recent activity
Analyzing
Block #84,490,012
25 transactions · 23 stateful · 2026-06-29 15:19:00 UTC
Parallelism
84/100
Blocked
30%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,490,012 · 25 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
1w06w17w211w012w113w215w316w119w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5049704f…406f
0x34b655…2a6f
6 touches
3 conflicts
0xfd4e2262…cd8c
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x1ff965a5…b3aa
0x34b655…2a6f
4 touches
1 conflict
0x206f4379…e08a
0x34b655…2a6f
4 touches
1 conflict
0x454d8940…cfe7
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 0x5049704f0d…dc406f
Audit this contract →
← previous block·next block →recent activity