← previous blocknext block →recent activity
Analyzing
Block #74,949,351
19 transactions · 15 stateful · 2026-05-16 10:29:03 UTC
Parallelism
68/100
Blocked
47%
Avg conflicts / tx
0.89
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #74,949,351 · 19 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
1w02w15w06w112w013w114w215w316w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x9a3801b1…a598
0x34b655…2a6f
8 touches
6 conflicts
0x90687d94…b524
0x34b655…2a6f
8 touches
6 conflicts
0xb9868b52…c77f
0x34b655…2a6f
6 touches
3 conflicts
0xba9f88e8…9c33
0x34b655…2a6f
6 touches
3 conflicts
0xd5b10148…e636
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x22e0cc1d…ad04
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity