← previous blocknext block →recent activity
Analyzing
Block #74,398,536
30 transactions · 18 stateful · 2026-05-13 21:08:56 UTC
Parallelism
80/100
Blocked
56%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #74,398,536 · 30 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
1w02w13w24w35w47w417w018w119w227w328w429w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x62d080e9…4a7c
0x34b655…2a6f
10 touches
10 conflicts
0xf853eb8e…4027
0x34b655…2a6f
10 touches
10 conflicts
0x9bcb27e8…919b
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002a
0x1b6862…e19c
8 touches
6 conflicts
0xb89c7e78…0bee
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
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
10 conflicts on slot 0x62d080e928…5a4a7c
Audit this contract →
← previous block·next block →recent activity