← previous blocknext block →recent activity
Analyzing
Block #73,210,037
16 transactions · 14 stateful · 2026-05-08 09:02:09 UTC
Parallelism
81/100
Blocked
29%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,210,037 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w19w010w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7f189cf6…afab
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xf908aa01…123d
0xd32edf…ff58
3 touches
1 conflict
0x3dfc05ee…a3e3
0x065c9d…c394
2 touches
0 conflicts
0x641e0fcf…233b
0x065c9d…c394
2 touches
0 conflicts
0x695cd256…2b70
0x065c9d…c394
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 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: Kuru Exchange: Market-MON/USDC
1 conflict on slot 0x7f189cf621…beafab
Audit this contract →
← previous block·next block →recent activity