← previous blocknext block →recent activity
Analyzing
Block #74,438,439
10 transactions · 9 stateful · 2026-05-14 01:34:33 UTC
Parallelism
70/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,438,439 · 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
1w02w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c8c6ab6…dc36
0x065c9d…c394
4 touches
1 conflict
0xffe431af…8faa
0x065c9d…c394
4 touches
1 conflict
0x76e559a4…77fb
0x2a68ba…90c5
4 touches
1 conflict
0x09f98366…ab8d
0x065c9d…c394
3 touches
1 conflict
0x99f666e3…b2a2
0x3bd359…433a
2 touches
0 conflicts
0x041215ce…b041
0x754704…b603
2 touches
0 conflicts
0x4ea8165a…9f57
0x754704…b603
2 touches
0 conflicts
0x59b08bb2…4632
0x754704…b603
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 0x5c8c6ab6f0…86dc36
Audit this contract →
← previous block·next block →recent activity