← previous blocknext block →recent activity
Analyzing
Block #73,336,146
13 transactions · 12 stateful · 2026-05-08 23:01:04 UTC
Parallelism
69/100
Blocked
25%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,336,146 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x9a78a80e…e7bb
0x065c9d…c394
4 touches
1 conflict
0xcb10f657…ba10
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x957465d7…cb31
0x065c9d…c394
4 touches
1 conflict
0x003e019f…10d3
0x065c9d…c394
3 touches
1 conflict
0x1be9de9e…8a09
0x065c9d…c394
3 touches
1 conflict
0xb11464b1…5786
0x065c9d…c394
3 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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity