← previous blocknext block →recent activity
Analyzing
Block #73,416,403
13 transactions · 12 stateful · 2026-05-09 07:55:07 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,416,403 · 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
1w06w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x58fbe85a…082e
0x065c9d…c394
4 touches
1 conflict
0x6f08361d…bda6
0x065c9d…c394
4 touches
1 conflict
0xdab0a5f1…e6f7
0x065c9d…c394
3 touches
1 conflict
0x16fa1aed…a82c
0x065c9d…c394
3 touches
1 conflict
0x2e4fbc37…b0d1
0x065c9d…c394
2 touches
0 conflicts
0x2e81835d…d789
0x065c9d…c394
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
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