← previous blocknext block →recent activity
Analyzing
Block #74,414,705
7 transactions · 5 stateful · 2026-05-13 22:56:31 UTC
Parallelism
71/100
Blocked
40%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,414,705 · 7 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
1w03w14w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7655e120…f5fa
0x065c9d…c394
4 touches
1 conflict
0x269b65af…bbfd
0x065c9d…c394
4 touches
1 conflict
0x3b18cda7…d0f7
0x065c9d…c394
3 touches
1 conflict
0x1c7e2597…8ed3
0x065c9d…c394
3 touches
1 conflict
0x5fbc5e27…d4ea
0x065c9d…c394
2 touches
0 conflicts
0xffe431af…8faa
0x065c9d…c394
2 touches
0 conflicts
0x046a928e…0012
0x2a68ba…90c5
2 touches
0 conflicts
0x30276c1c…47b4
0x2a68ba…90c5
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 0x7655e12080…aef5fa
Audit this contract →
← previous block·next block →recent activity