← previous blocknext block →recent activity
Analyzing
Block #74,787,898
16 transactions · 14 stateful · 2026-05-15 16:31:43 UTC
Parallelism
69/100
Blocked
36%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #74,787,898 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w18w39w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x8315ff4a…fdcc
0xd32edf…ff58
3 touches
1 conflict
0x441a1ad5…855e
0x065c9d…c394
2 touches
0 conflicts
0x4698c00f…01a6
0x065c9d…c394
2 touches
0 conflicts
0x715670b8…788b
0x065c9d…c394
2 touches
0 conflicts
0xc5a979b9…abb2
0x065c9d…c394
2 touches
0 conflicts
0xd35dfb01…1e23
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity