← previous blocknext block →recent activity
Analyzing
Block #74,025,692
24 transactions · 19 stateful · 2026-05-12 03:48:49 UTC
Parallelism
75/100
Blocked
47%
Avg conflicts / tx
1.04
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #74,025,692 · 24 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
4w05w16w210w011w112w213w314w415w518w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
12 touches
15 conflicts
0x0b390c61…dc07
0x065c9d…c394
10 touches
10 conflicts
0xbd7e37a9…9eb5
0x065c9d…c394
8 touches
6 conflicts
0x765c236f…ff45
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x5de96bd3…c60c
0x34b655…2a6f
4 touches
1 conflict
0x8db1e0f2…2fcf
0x34b655…2a6f
4 touches
1 conflict
0x9be2b99a…a959
0x34b655…2a6f
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: Perpl
15 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity