← previous blocknext block →recent activity
Analyzing
Block #73,387,440
14 transactions · 14 stateful · 2026-05-09 04:42:16 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,387,440 · 14 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
1w06w17w28w19w3
- 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
0xceaabde6…3aa2
0x065c9d…c394
4 touches
1 conflict
0x1bc249be…6adb
0x065c9d…c394
4 touches
1 conflict
0xbc5f471a…0c29
0x065c9d…c394
4 touches
1 conflict
0xf0ac4807…f292
0x065c9d…c394
3 touches
1 conflict
0xb9cfccb3…5776
0x065c9d…c394
3 touches
1 conflict
0x94c1e281…d21e
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: MarginAccount
3 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity