← previous blocknext block →recent activity
Analyzing
Block #74,635,883
13 transactions · 13 stateful · 2026-05-14 23:36:35 UTC
Parallelism
85/100
Blocked
15%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,635,883 · 13 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
1w010w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17db803d…e2d6
0x065c9d…c394
4 touches
1 conflict
0x5c8c6ab6…dc36
0x065c9d…c394
4 touches
1 conflict
0x47a92def…6d94
0x065c9d…c394
3 touches
1 conflict
0xd36a6831…ba31
0x065c9d…c394
3 touches
1 conflict
0x0bafbae4…db64
0x065c9d…c394
2 touches
0 conflicts
0xab2a4f47…02c3
0x065c9d…c394
2 touches
0 conflicts
0xb3c6f480…53d5
0x065c9d…c394
2 touches
0 conflicts
0xc620214b…51b3
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 0x17db803d5d…c0e2d6
Audit this contract →
← previous block·next block →recent activity