← previous blocknext block →recent activity
Analyzing
Block #73,807,418
10 transactions · 9 stateful · 2026-05-11 03:32:59 UTC
Parallelism
60/100
Blocked
33%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,807,418 · 10 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
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x22e295f5…1bef
0x065c9d…c394
4 touches
1 conflict
0x8765d912…1572
0x065c9d…c394
4 touches
1 conflict
0x416dad00…9fe5
0x065c9d…c394
4 touches
1 conflict
0xccf51b68…3a23
0x065c9d…c394
3 touches
1 conflict
0x132925b7…7fbe
0x065c9d…c394
3 touches
1 conflict
0x49b5f107…9c40
0x065c9d…c394
3 touches
1 conflict
0x99b9ede9…64f4
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 0x046a928e85…e50012
Audit this contract →
← previous block·next block →recent activity