← previous blocknext block →recent activity
Analyzing
Block #74,918,224
26 transactions · 22 stateful · 2026-05-16 07:00:53 UTC
Parallelism
77/100
Blocked
73%
Avg conflicts / tx
1.5
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #74,918,224 · 26 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
1w02w13w24w35w06w37w08w19w111w012w113w214w315w418w419w420w521w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
10 touches
10 conflicts
0x348fda08…7e96
0x065c9d…c394
10 touches
10 conflicts
0x3e49348b…9445
0x34b655…2a6f
10 touches
10 conflicts
0xba38536d…2b7d
0x065c9d…c394
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002d
0x1b6862…e19c
8 touches
6 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: Perpl
10 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity