← previous blocknext block →recent activity
Analyzing
Block #74,420,571
20 transactions · 17 stateful · 2026-05-13 23:35:30 UTC
Parallelism
75/100
Blocked
35%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #74,420,571 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w08w09w111w213w314w315w418w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x31bf71ad…0f99
0xd32edf…ff58
7 touches
6 conflicts
0x5c8c6ab6…dc36
0x065c9d…c394
6 touches
3 conflicts
0xcd510377…571e
0xee8c0e…1242
4 touches
1 conflict
0x00000000…0003
0xb02793…e402
4 touches
1 conflict
0x00000000…0004
0xb02793…e402
4 touches
1 conflict
0x56a919c4…ab49
0xee8c0e…1242
4 touches
1 conflict
0xffe431af…8faa
0x065c9d…c394
4 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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity