← previous blocknext block →recent activity
Analyzing
Block #74,502,857
18 transactions · 14 stateful · 2026-05-14 08:43:23 UTC
Parallelism
89/100
Blocked
14%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,502,857 · 18 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
2w08w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf0912933…682f
0x065c9d…c394
4 touches
1 conflict
0x5c8c6ab6…dc36
0x065c9d…c394
4 touches
1 conflict
0xc6483707…00f1
0x065c9d…c394
3 touches
1 conflict
0xe1eb3de1…b9f0
0x065c9d…c394
3 touches
1 conflict
0x0b44e09d…9c4f
0x065c9d…c394
2 touches
0 conflicts
0x20cafa32…98c1
0x065c9d…c394
2 touches
0 conflicts
0x32b3e556…42aa
0x065c9d…c394
2 touches
0 conflicts
0x364ecc37…679b
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 0xf0912933eb…88682f
Audit this contract →
← previous block·next block →recent activity