← previous blocknext block →recent activity
Analyzing
Block #74,025,610
8 transactions · 8 stateful · 2026-05-12 03:48:16 UTC
Parallelism
50/100
Blocked
50%
Avg conflicts / tx
0.75
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #74,025,610 · 8 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
1w02w13w15w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x765c236f…ff45
0x2a68ba…90c5
6 touches
3 conflicts
0x522cdec1…f274
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b390c61…dc07
0x065c9d…c394
4 touches
1 conflict
0x05eea3e3…5846
0x2a68ba…90c5
4 touches
1 conflict
0x99c79b47…d79b
0x065c9d…c394
3 touches
1 conflict
0x865ae6ab…912c
0x065c9d…c394
3 touches
1 conflict
0xda47e09b…91e7
0xd32edf…ff58
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 0x765c236f2d…b5ff45
Audit this contract →
← previous block·next block →recent activity