← previous blocknext block →recent activity
Analyzing
Block #74,788,175
20 transactions · 15 stateful · 2026-05-15 16:33:34 UTC
Parallelism
80/100
Blocked
53%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #74,788,175 · 20 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
1w02w14w28w09w011w112w213w215w116w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8e594d49…0f8f
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf06c2cf5…61bd
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x84fb2a36…db89
0x34b655…2a6f
5 touches
3 conflicts
0xe18974ca…ed52
0xd32edf…ff58
5 touches
3 conflicts
0xcb45d9d6…cb82
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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
6 conflicts on slot 0x8e594d4936…660f8f
Audit this contract →
← previous block·next block →recent activity