← previous blocknext block →recent activity
Analyzing
Block #74,441,695
21 transactions · 20 stateful · 2026-05-14 01:56:15 UTC
Parallelism
71/100
Blocked
50%
Avg conflicts / tx
1.33
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #74,441,695 · 21 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
1w02w13w24w38w49w513w016w117w218w319w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3981be5…2c47
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xf109643f…ed73
0xd32edf…ff58
9 touches
10 conflicts
0xb8228d38…3953
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0x5c8c6ab6…dc36
0x065c9d…c394
8 touches
6 conflicts
0x00000000…002b
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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: Perpl
15 conflicts on slot 0xf3981be56e…f02c47
Audit this contract →
← previous block·next block →recent activity