← previous blocknext block →recent activity
Analyzing
Block #73,804,700
47 transactions · 35 stateful · 2026-05-11 03:14:52 UTC
Parallelism
72/100
Blocked
69%
Avg conflicts / tx
1.85
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #73,804,700 · 47 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w06w110w013w014w115w216w017w222w023w124w225w326w227w328w429w530w633w136w437w538w642w844w1045w1146w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x157b6348…8604
0x34b655…2a6f
16 touches
28 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
14 touches
21 conflicts
0xac2a0273…721b
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x7d18194f…2b8c
0xd32edf…ff58
11 touches
15 conflicts
0x7cb2f3fa…4836
0x34b655…2a6f
8 touches
6 conflicts
0xf8f1e808…a4fd
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…001e
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
28 conflicts on slot 0x157b634872…098604
Audit this contract →
← previous block·next block →recent activity