← previous blocknext block →recent activity
Analyzing
Block #74,461,041
22 transactions · 16 stateful · 2026-05-14 04:05:00 UTC
Parallelism
73/100
Blocked
50%
Avg conflicts / tx
0.86
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #74,461,041 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w510w011w112w213w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
12 touches
15 conflicts
0xa472d565…9fe4
0x3bd359…433a
6 touches
3 conflicts
0x44ad89ba…cf83
0x5c2513…7777
6 touches
3 conflicts
0xce2b6650…ecc3
0x5c2513…7777
6 touches
3 conflicts
0x00c46468…f328
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0001
0xcc67aa…c71c
6 touches
3 conflicts
0x00000000…0000
0xcc67aa…c71c
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
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: 0xab35264b…1cfa38
15 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity