← previous blocknext block →recent activity
Analyzing
Block #84,356,700
10 transactions · 8 stateful · 2026-06-29 00:30:18 UTC
Parallelism
70/100
Blocked
38%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,356,700 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5ba636e7…427e
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x8a7af3fd…72a7
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x8a7af3fd…72a6
0x34b655…2a6f
4 touches
1 conflict
0x601978e3…1979
0x34b655…2a6f
3 touches
1 conflict
0xf506180e…9469
0x34b655…2a6f
3 touches
1 conflict
0x48e96923…1a2f
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 0x5ba636e799…2e427e
Audit this contract →
← previous block·next block →recent activity