← previous blocknext block →recent activity
Analyzing
Block #84,563,103
20 transactions · 15 stateful · 2026-06-29 23:27:00 UTC
Parallelism
70/100
Blocked
60%
Avg conflicts / tx
0.8
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #84,563,103 · 20 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
1w02w03w15w06w19w010w111w215w116w217w318w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x98d58911…19f2
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xacb691b6…8e39
0x34b655…2a6f
8 touches
6 conflicts
0xdc120748…ff36
0xa6afd3…d132
6 touches
3 conflicts
0xa42e8482…b88f
0x34b655…2a6f
6 touches
3 conflicts
0xf1878dfb…5baf
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x424eca3b…f2ab
0xa6afd3…d132
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
6 conflicts on slot 0x98d589117f…0c19f2
Audit this contract →
← previous block·next block →recent activity