← previous blocknext block →recent activity
Analyzing
Block #74,726,984
16 transactions · 13 stateful · 2026-05-15 09:44:17 UTC
Parallelism
75/100
Blocked
46%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #74,726,984 · 16 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
1w03w14w05w28w19w010w312w315w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x801a6e57…d85c
0x34b655…2a6f
4 touches
1 conflict
0xbcd06717…bfb7
0x065c9d…c394
4 touches
1 conflict
0x47b807a2…3307
0x065c9d…c394
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x2601c0e3…66b5
0x065c9d…c394
4 touches
1 conflict
0x41755291…977f
0x065c9d…c394
4 touches
1 conflict
0xc34e9528…edd5
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity