← previous blocknext block →recent activity
Analyzing
Block #74,427,726
21 transactions · 16 stateful · 2026-05-14 00:23:09 UTC
Parallelism
86/100
Blocked
25%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,427,726 · 21 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
3w05w17w010w113w014w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x24968e6d…0132
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xc17bf20f…8c64
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0xc7dbfda6…4f6c
0xd32edf…ff58
3 touches
1 conflict
0xbe29f7a9…ae80
0x065c9d…c394
3 touches
1 conflict
0x609fd81d…41ce
0x065c9d…c394
3 touches
1 conflict
0x87d4bb26…84eb
0x065c9d…c394
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: Market-MON/USDC
3 conflicts on slot 0x24968e6db4…f00132
Audit this contract →
← previous block·next block →recent activity