← previous blocknext block →recent activity
Analyzing
Block #74,427,728
16 transactions · 11 stateful · 2026-05-14 00:23:10 UTC
Parallelism
81/100
Blocked
27%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,427,728 · 16 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
1w02w17w210w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0xfa28e836…cb0f
0xd32edf…ff58
3 touches
1 conflict
0x0981d379…a9a3
0x065c9d…c394
2 touches
0 conflicts
0x36f6fac1…1548
0x065c9d…c394
2 touches
0 conflicts
0x6bacc0aa…efea
0x065c9d…c394
2 touches
0 conflicts
0x82754758…a06b
0x065c9d…c394
2 touches
0 conflicts
0x9884184f…3be2
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity