← previous blocknext block →recent activity
Analyzing
Block #73,693,910
12 transactions · 12 stateful · 2026-05-10 14:47:23 UTC
Parallelism
50/100
Blocked
42%
Avg conflicts / tx
1.25
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #73,693,910 · 12 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
2w03w17w28w39w410w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0x0ac31945…2c72
0x065c9d…c394
10 touches
10 conflicts
0x529acb6a…fcc6
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xed57bddf…1abf
0xc8689a…ee79
4 touches
1 conflict
0x59c66a78…3ef3
0x065c9d…c394
4 touches
1 conflict
0xade2ada8…c261
0x065c9d…c394
4 touches
1 conflict
0xae69c125…2379
0x2a68ba…90c5
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: Kuru Exchange: Market-MON/USDC
15 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity