← previous blocknext block →recent activity
Analyzing
Block #74,025,182
7 transactions · 5 stateful · 2026-05-12 03:45:24 UTC
Parallelism
71/100
Blocked
40%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,025,182 · 7 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
1w02w13w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3870dbe…bef3
0x2a68ba…90c5
4 touches
1 conflict
0xbd7e37a9…9eb5
0x065c9d…c394
4 touches
1 conflict
0x84494d31…d133
0xd32edf…ff58
3 touches
1 conflict
0x874d2ef6…9b06
0x065c9d…c394
2 touches
1 conflict
0x122b2525…1e60
0x065c9d…c394
2 touches
0 conflicts
0x17e63c13…80c1
0x065c9d…c394
2 touches
0 conflicts
0xec2e0604…737f
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
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 0xb3870dbe63…c9bef3
Audit this contract →
← previous block·next block →recent activity