← previous blocknext block →recent activity
Analyzing
Block #74,525,445
13 transactions · 9 stateful · 2026-05-14 11:15:32 UTC
Parallelism
85/100
Blocked
33%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,525,445 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w08w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xa02838a3…bc54
0x34b655…2a6f
4 touches
1 conflict
0x47b807a2…3307
0x065c9d…c394
4 touches
1 conflict
0x28dde4ce…6ae3
0x065c9d…c394
3 touches
1 conflict
0x9888a489…adb8
0x065c9d…c394
2 touches
0 conflicts
0x9df6d06b…85e7
0x065c9d…c394
2 touches
0 conflicts
0xbcb7830b…c06f
0x065c9d…c394
2 touches
0 conflicts
0xc543ec63…7299
0x065c9d…c394
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
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity