← previous blocknext block →recent activity
Analyzing
Block #74,796,816
8 transactions · 7 stateful · 2026-05-15 17:31:14 UTC
Parallelism
63/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,796,816 · 8 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
1w02w13w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x41755291…977f
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x26da0f84…3c33
0x065c9d…c394
3 touches
1 conflict
0x3b002d0b…9e93
0x065c9d…c394
3 touches
1 conflict
0x59fcabe2…631a
0x065c9d…c394
2 touches
0 conflicts
0x8929e90a…7d8c
0x065c9d…c394
2 touches
0 conflicts
0xd2931029…e57a
0x065c9d…c394
2 touches
0 conflicts
0xde28bf24…8d30
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
3 conflicts on slot 0x4175529119…79977f
Audit this contract →
← previous block·next block →recent activity