← previous blocknext block →recent activity
Analyzing
Block #84,285,429
13 transactions · 11 stateful · 2026-06-28 16:35:22 UTC
Parallelism
77/100
Blocked
18%
Avg conflicts / tx
0.15
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,285,429 · 13 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
4w010w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcd63138b…63d9
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xec71d7fa…def3
0x34b655…2a6f
4 touches
1 conflict
0xf1b8c26d…5189
0x34b655…2a6f
4 touches
1 conflict
0x421a0de8…e035
0x34b655…2a6f
4 touches
1 conflict
0xab86573c…682e
0x34b655…2a6f
4 touches
1 conflict
0x1c9c7cbc…d3c8
0x34b655…2a6f
2 touches
0 conflicts
0x242bdfb5…974d
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0xcd63138b1f…b763d9
Audit this contract →
← previous block·next block →recent activity