← previous blocknext block →recent activity
Analyzing
Block #84,334,333
26 transactions · 26 stateful · 2026-06-28 22:01:09 UTC
Parallelism
69/100
Blocked
35%
Avg conflicts / tx
0.92
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #84,334,333 · 26 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w010w011w112w113w217w318w421w522w623w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x32229dd3…4dbb
0x34b655…2a6f
6 touches
3 conflicts
0x23ab8481…52d5
0x34b655…2a6f
6 touches
3 conflicts
0x9fa1409b…0e54
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x22e0cc1d…ad0d
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity