← previous blocknext block →recent activity
Analyzing
Block #73,642,469
19 transactions · 16 stateful · 2026-05-10 09:00:26 UTC
Parallelism
63/100
Blocked
63%
Avg conflicts / tx
1.26
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #73,642,469 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w18w29w310w413w214w215w316w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa91c899f…6ee3
0x34b655…2a6f
12 touches
15 conflicts
0xc6417de0…2191
0xc8689a…ee79
10 touches
10 conflicts
0x57de3828…3fbb
0x34b655…2a6f
10 touches
10 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
10 touches
10 conflicts
0x6eba5e7f…4b52
0x34b655…2a6f
10 touches
10 conflicts
0x9753c6ec…6479
0x34b655…2a6f
10 touches
10 conflicts
0xedb848fe…6534
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 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
15 conflicts on slot 0xa91c899f02…fa6ee3
Audit this contract →
← previous block·next block →recent activity