← previous blocknext block →recent activity
Analyzing
Block #74,291,084
13 transactions · 13 stateful · 2026-05-13 09:14:02 UTC
Parallelism
77/100
Blocked
23%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,291,084 · 13 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
1w06w17w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xf823e97f…2ee6
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x366916da…6444
0x065c9d…c394
3 touches
1 conflict
0x50fa897b…2474
0x065c9d…c394
3 touches
1 conflict
0xc57c96c7…2985
0x065c9d…c394
3 touches
1 conflict
0x765c236f…ff45
0x2a68ba…90c5
2 touches
0 conflicts
0x10814d14…cdda
0x34b655…2a6f
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity