← previous blocknext block →recent activity
Analyzing
Block #74,452,574
9 transactions · 7 stateful · 2026-05-14 03:08:38 UTC
Parallelism
67/100
Blocked
43%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,452,574 · 9 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w16w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x1dff1919…fdfa
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0xffe431af…8faa
0x065c9d…c394
4 touches
1 conflict
0x9112d0cc…6973
0x065c9d…c394
3 touches
1 conflict
0x5cd401db…3805
0x065c9d…c394
2 touches
0 conflicts
0x9d0bb05b…debb
0x065c9d…c394
2 touches
0 conflicts
0x30276c1c…47b4
0x2a68ba…90c5
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: Market-MON/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity