← previous blocknext block →recent activity
Analyzing
Block #74,470,064
9 transactions · 7 stateful · 2026-05-14 05:04:59 UTC
Parallelism
78/100
Blocked
14%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,470,064 · 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c8c6ab6…dc36
0x065c9d…c394
4 touches
1 conflict
0x765c236f…ff45
0x2a68ba…90c5
4 touches
1 conflict
0xc0d821ae…2df9
0x065c9d…c394
3 touches
1 conflict
0x36075cb1…467e
0x065c9d…c394
2 touches
0 conflicts
0x8386405e…7da7
0x065c9d…c394
2 touches
0 conflicts
0x93521554…6195
0x065c9d…c394
2 touches
0 conflicts
0xc2af0031…2947
0x065c9d…c394
2 touches
0 conflicts
0x01e7b865…6e6d
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 0x5c8c6ab6f0…86dc36
Audit this contract →
← previous block·next block →recent activity