← previous blocknext block →recent activity
Analyzing
Block #73,596,003
11 transactions · 9 stateful · 2026-05-10 03:49:24 UTC
Parallelism
64/100
Blocked
44%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,596,003 · 11 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
2w06w17w28w39w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x012980b4…ba5a
0x065c9d…c394
4 touches
1 conflict
0x4d87512b…897c
0x065c9d…c394
4 touches
1 conflict
0xb2034294…06ab
0x065c9d…c394
4 touches
1 conflict
0x47c18ce2…aa96
0x065c9d…c394
3 touches
1 conflict
0xd57ed946…df0b
0x065c9d…c394
3 touches
1 conflict
0xfbe396f6…b2d0
0x065c9d…c394
3 touches
1 conflict
0x2a780b38…3ce4
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