← previous blocknext block →recent activity
Analyzing
Block #84,488,827
8 transactions · 7 stateful · 2026-06-29 15:11:08 UTC
Parallelism
75/100
Blocked
29%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,488,827 · 8 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
1w02w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x39fa7a0d…33a4
0x34b655…2a6f
4 touches
1 conflict
0xa2ed607d…4d45
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xffc2f21e…b393
0x34b655…2a6f
4 touches
1 conflict
0x18c610ca…b213
0x34b655…2a6f
2 touches
0 conflicts
0x1edf5c88…ec72
0x34b655…2a6f
2 touches
0 conflicts
0x20e57a61…028c
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
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 0x39fa7a0d46…b633a4
Audit this contract →
← previous block·next block →recent activity