← previous blocknext block →recent activity
Analyzing
Block #74,586,016
25 transactions · 23 stateful · 2026-05-14 18:03:18 UTC
Parallelism
76/100
Blocked
65%
Avg conflicts / tx
1.56
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #74,586,016 · 25 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
1w02w13w14w26w08w09w110w211w312w413w517w218w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
12 touches
15 conflicts
0xf853eb8e…4027
0x34b655…2a6f
10 touches
10 conflicts
0xa91c899f…6ee3
0x34b655…2a6f
10 touches
10 conflicts
0xb3e0ed54…a596
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…002e
0x1b6862…e19c
6 touches
3 conflicts
0x14d1bf0e…e09f
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x7cab84dd…a441
0x34b655…2a6f
6 touches
3 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: 0xab35264b…1cfa38
15 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity