← previous blocknext block →recent activity
Analyzing
Block #74,452,773
23 transactions · 18 stateful · 2026-05-14 03:09:57 UTC
Parallelism
83/100
Blocked
39%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #74,452,773 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w111w013w014w115w220w121w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c389468…6b0e
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xa472d565…9fe4
0x3bd359…433a
6 touches
3 conflicts
0xce2b6650…ecc3
0x5c2513…7777
6 touches
3 conflicts
0x44ad89ba…cf83
0x5c2513…7777
6 touches
3 conflicts
0x00c46468…f328
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0000
0xcc67aa…c71c
6 touches
3 conflicts
0x00000000…0001
0xcc67aa…c71c
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
3 conflicts on slot 0x1c38946843…a16b0e
Audit this contract →
← previous block·next block →recent activity