← previous blocknext block →recent activity
Analyzing
Block #73,698,003
13 transactions · 12 stateful · 2026-05-10 15:14:59 UTC
Parallelism
85/100
Blocked
25%
Avg conflicts / tx
0.31
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,698,003 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w06w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc9e97522…3519
0x2a68ba…90c5
4 touches
1 conflict
0x3e733ae4…4598
0x34b655…2a6f
4 touches
1 conflict
0x0ac31945…2c72
0x065c9d…c394
4 touches
1 conflict
0xce4ab369…801c
0xd32edf…ff58
3 touches
1 conflict
0x529acb6a…fcc6
0x065c9d…c394
2 touches
0 conflicts
0xe3012deb…de6d
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
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
1 conflict on slot 0xc9e9752290…9c3519
Audit this contract →
← previous block·next block →recent activity