← previous blocknext block →recent activity
Analyzing
Block #73,663,661
21 transactions · 13 stateful · 2026-05-10 11:23:12 UTC
Parallelism
71/100
Blocked
46%
Avg conflicts / tx
0.71
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #73,663,661 · 21 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
1w07w08w113w117w218w319w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38524fae…9deb
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x96b01960…163d
0x34b655…2a6f
4 touches
1 conflict
0x97d5efed…1aa4
0x34b655…2a6f
4 touches
1 conflict
0xa91c899f…6ee3
0x34b655…2a6f
4 touches
1 conflict
0xf2a139df…1eb3
0x34b655…2a6f
4 touches
1 conflict
0xf7c5003c…8dc0
0x34b655…2a6f
4 touches
1 conflict
0x7f81fb82…633e
0x065c9d…c394
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
10 conflicts on slot 0x38524faed4…ae9deb
Audit this contract →
← previous block·next block →recent activity