← previous blocknext block →recent activity
Analyzing
Block #74,238,847
9 transactions · 8 stateful · 2026-05-13 03:26:42 UTC
Parallelism
78/100
Blocked
38%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,238,847 · 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
1w04w05w16w07w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x768cffcd…2648
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x11a67036…1c34
0x065c9d…c394
2 touches
0 conflicts
0x5c09f996…4af6
0x065c9d…c394
2 touches
0 conflicts
0x8f0597dc…2893
0x065c9d…c394
2 touches
0 conflicts
0xbf0a7a6a…3a53
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 0x046a928e85…e50012
Audit this contract →
← previous block·next block →recent activity