← previous blocknext block →recent activity
Analyzing
Block #74,429,793
6 transactions · 5 stateful · 2026-05-14 00:36:56 UTC
Parallelism
67/100
Blocked
40%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,429,793 · 6 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
1w02w15w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x765c236f…ff45
0x2a68ba…90c5
4 touches
1 conflict
0x322c951a…0d56
0x065c9d…c394
3 touches
1 conflict
0xfb26faa4…7cac
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x24968e6d…0132
0x065c9d…c394
2 touches
0 conflicts
0x402d297a…12ac
0x065c9d…c394
2 touches
0 conflicts
0x9597ae4a…2bf0
0x065c9d…c394
2 touches
0 conflicts
0x973ca0b0…e67c
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