← previous blocknext block →recent activity
Analyzing
Block #74,025,170
9 transactions · 5 stateful · 2026-05-12 03:45:19 UTC
Parallelism
78/100
Blocked
20%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,025,170 · 9 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x765c236f…ff45
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0f4455c1…59a9
0x065c9d…c394
3 touches
1 conflict
0x0b390c61…dc07
0x065c9d…c394
2 touches
0 conflicts
0x1aee96c6…124f
0x065c9d…c394
2 touches
0 conflicts
0x1d5478ec…d851
0x065c9d…c394
2 touches
0 conflicts
0x22dbf14a…223d
0x065c9d…c394
2 touches
0 conflicts
0x7d8b5c38…4303
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
1 conflict on slot 0x765c236f2d…b5ff45
Audit this contract →
← previous block·next block →recent activity