← previous blocknext block →recent activity
Analyzing
Block #74,957,281
11 transactions · 11 stateful · 2026-05-16 11:22:20 UTC
Parallelism
45/100
Blocked
64%
Avg conflicts / tx
1.55
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #74,957,281 · 11 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
1w02w13w24w06w17w28w39w410w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x3e49348b…9445
0x34b655…2a6f
10 touches
10 conflicts
0x348fda08…7e96
0x065c9d…c394
6 touches
3 conflicts
0x97b0b2ee…4666
0x34b655…2a6f
6 touches
3 conflicts
0xcf55ee9e…efaf
0x34b655…2a6f
6 touches
3 conflicts
0xffd39455…672a
0x065c9d…c394
4 touches
1 conflict
0x2471363a…406e
0x34b655…2a6f
4 touches
1 conflict
0x7150753f…7e32
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity