← previous blocknext block →recent activity
Analyzing
Block #84,358,233
31 transactions · 21 stateful · 2026-06-29 00:40:32 UTC
Parallelism
81/100
Blocked
52%
Avg conflicts / tx
0.68
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #84,358,233 · 31 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w112w013w114w216w017w018w119w020w121w222w126w227w328w429w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92793b0e…b68e
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x5a630301…e94f
0x34b655…2a6f
6 touches
3 conflicts
0x9966da31…0d0f
0x34b655…2a6f
6 touches
3 conflicts
0x62d66091…2384
0x34b655…2a6f
6 touches
3 conflicts
0xd16ba145…d030
0x34b655…2a6f
6 touches
3 conflicts
0xe59df86b…a00c
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x92793b0ede…0ab68e
Audit this contract →
← previous block·next block →recent activity