← previous blocknext block →recent activity
Analyzing
Block #74,902,855
10 transactions · 9 stateful · 2026-05-16 05:18:26 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,902,855 · 10 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfc3f1f0c…dc3e
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf9228bf4…635b
0x065c9d…c394
3 touches
1 conflict
0x08f09939…fc5f
0x065c9d…c394
3 touches
1 conflict
0x518f2dd1…53e0
0x065c9d…c394
2 touches
0 conflicts
0x97baf7d5…6c14
0x065c9d…c394
2 touches
0 conflicts
0xfe2bac2b…2cec
0x065c9d…c394
2 touches
0 conflicts
0x30276c1c…47b4
0x2a68ba…90c5
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 0xfc3f1f0cd0…84dc3e
Audit this contract →
← previous block·next block →recent activity