← previous blocknext block →recent activity
Analyzing
Block #84,316,259
13 transactions · 8 stateful · 2026-06-28 20:00:41 UTC
Parallelism
85/100
Blocked
13%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,316,259 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
11w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5138188e…796b
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x8607b9d8…ad3b
0x34b655…2a6f
4 touches
1 conflict
0x72a152dd…9dac
0x16f70c…c3dd
2 touches
0 conflicts
0x00000000…000b
0x302202…b3be
2 touches
0 conflicts
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x03f7f275…1a9e
0x34b655…2a6f
2 touches
0 conflicts
0x1993f91a…d7e2
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 0x5138188e69…d6796b
Audit this contract →
← previous block·next block →recent activity