← previous blocknext block →recent activity
Analyzing
Block #74,923,766
9 transactions · 8 stateful · 2026-05-16 07:38:00 UTC
Parallelism
78/100
Blocked
38%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,923,766 · 9 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
1w02w15w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x233ee01d…eb47
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x765c236f…ff45
0x2a68ba…90c5
4 touches
1 conflict
0x4e500776…ad0e
0x065c9d…c394
3 touches
1 conflict
0xb6e3bf47…74d0
0x065c9d…c394
3 touches
1 conflict
0xd52d5879…be9c
0x065c9d…c394
2 touches
0 conflicts
0xe0506c26…c1c1
0x065c9d…c394
2 touches
0 conflicts
0x00f7e3b7…e015
0x188d58…ea8e
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 0x233ee01d95…aaeb47
Audit this contract →
← previous block·next block →recent activity