← previous blocknext block →recent activity
Analyzing
Block #75,254,267
22 transactions · 21 stateful · 2026-05-17 20:25:41 UTC
Parallelism
18/100
Blocked
81%
Avg conflicts / tx
6.95
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #75,254,267 · 22 txs across 18 waves · depth 18
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w911w1012w1113w1214w1315w1416w1517w1618w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0001
0x86dfd5…6a7d
36 touches
153 conflicts
0x00000000…0003
0x86dfd5…6a7d
36 touches
153 conflicts
0x1686502b…a1d2
0x3bd359…433a
36 touches
153 conflicts
0x1d4c90ab…1ba7
0xb72e62…7777
36 touches
153 conflicts
0x00000000…0000
0x86dfd5…6a7d
36 touches
153 conflicts
0x1ccd1b02…31fd
0x34b655…2a6f
2 touches
0 conflicts
0x414e9446…4b59
0x34b655…2a6f
2 touches
0 conflicts
0x478cdc57…5f1d
0x34b655…2a6f
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: 0x86dfd554…906a7d
153 conflicts on slot 0x0000000000…000001
Audit this contract →
← previous block·next block →recent activity