← previous blocknext block →recent activity
Analyzing
Block #84,354,482
24 transactions · 18 stateful · 2026-06-29 00:15:30 UTC
Parallelism
79/100
Blocked
56%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,354,482 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w29w010w112w313w114w116w219w220w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5f3fc680…f989
0x34b655…2a6f
8 touches
6 conflicts
0x7b06e58f…aefe
0xd32edf…ff58
7 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x9966da31…0d0f
0x34b655…2a6f
4 touches
1 conflict
0x3f7ad3a0…de3b
0x34b655…2a6f
4 touches
1 conflict
0xd2274a53…9d6a
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 0x5f3fc68024…49f989
Audit this contract →
← previous block·next block →recent activity