← previous blocknext block →recent activity
Analyzing
Block #74,900,174
10 transactions · 9 stateful · 2026-05-16 05:00:33 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,900,174 · 10 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
1w04w16w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xcaa9c77a…7146
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x44785379…a940
0x065c9d…c394
3 touches
1 conflict
0x4115090c…b752
0x065c9d…c394
3 touches
1 conflict
0x44ec9b38…dd72
0x065c9d…c394
3 touches
1 conflict
0xf6ee0ebe…539f
0x065c9d…c394
3 touches
1 conflict
0x765c236f…ff45
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity