← previous blocknext block →recent activity
Analyzing
Block #74,899,696
6 transactions · 6 stateful · 2026-05-16 04:57:21 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,899,696 · 6 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
1w03w14w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1a78bc67…600d
0x065c9d…c394
4 touches
1 conflict
0x64e92e59…412e
0x065c9d…c394
3 touches
1 conflict
0x6a164e0d…2bf4
0x065c9d…c394
3 touches
1 conflict
0xe438cfc1…804d
0x065c9d…c394
3 touches
1 conflict
0x088b1c71…940c
0x065c9d…c394
2 touches
0 conflicts
0x32d1672e…3078
0x065c9d…c394
2 touches
0 conflicts
0x4d9dc82c…ceb1
0x065c9d…c394
2 touches
0 conflicts
0x84c54cab…769a
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 0x1a78bc6762…79600d
Audit this contract →
← previous block·next block →recent activity