← previous blocknext block →recent activity
Analyzing
Block #74,555,613
28 transactions · 14 stateful · 2026-05-14 14:39:01 UTC
Parallelism
86/100
Blocked
43%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #74,555,613 · 28 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
1w02w16w216w017w121w123w324w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3d7a307…4d63
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xc59210c3…ab70
0x065c9d…c394
6 touches
3 conflicts
0x6eb217a1…903b
0x065c9d…c394
5 touches
3 conflicts
0xfe2bac2b…2cec
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
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 0xf3d7a307cc…f14d63
Audit this contract →
← previous block·next block →recent activity