← previous blocknext block →recent activity
Analyzing
Block #73,348,006
14 transactions · 14 stateful · 2026-05-09 00:19:58 UTC
Parallelism
79/100
Blocked
14%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,348,006 · 14 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
3w05w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x4d87512b…897c
0x065c9d…c394
4 touches
1 conflict
0x1bdac316…b53f
0x065c9d…c394
4 touches
1 conflict
0x3c649c5b…52f7
0x065c9d…c394
3 touches
1 conflict
0xfe830be8…1518
0x065c9d…c394
3 touches
1 conflict
0xf993804e…80c1
0x065c9d…c394
2 touches
0 conflicts
0xbdff944d…447e
0x2a68ba…90c5
2 touches
0 conflicts
0x00000000…000b
0x3b1269…7ab7
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: MarginAccount
3 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity