← previous blocknext block →recent activity
Analyzing
Block #73,706,561
25 transactions · 21 stateful · 2026-05-10 16:12:43 UTC
Parallelism
80/100
Blocked
57%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,706,561 · 25 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
1w02w03w14w26w09w010w111w015w116w217w318w119w220w321w123w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaa8a1c54…ead3
0x34b655…2a6f
8 touches
6 conflicts
0x2923f0e9…f0d1
0xd32edf…ff58
7 touches
6 conflicts
0x08943ea2…ed03
0x754704…b603
6 touches
3 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002d
0x1b6862…e19c
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: Perpl
6 conflicts on slot 0xaa8a1c5424…edead3
Audit this contract →
← previous block·next block →recent activity