← previous blocknext block →recent activity
Analyzing
Block #84,575,418
21 transactions · 20 stateful · 2026-06-30 00:49:07 UTC
Parallelism
76/100
Blocked
55%
Avg conflicts / tx
0.81
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,575,418 · 21 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
1w02w03w15w26w37w010w011w113w114w116w117w218w319w420w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xd637b3…4160
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x309ef367…e8a1
0x34b655…2a6f
4 touches
1 conflict
0x388f889f…a655
0x34b655…2a6f
4 touches
1 conflict
0x765a2788…5478
0x34b655…2a6f
4 touches
1 conflict
0xa9ad4c70…1120
0x34b655…2a6f
4 touches
1 conflict
0xaa48195d…ffee
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: 0xd637b38f…c64160
6 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity