← previous blocknext block →recent activity
Analyzing
Block #75,863,422
19 transactions · 17 stateful · 2026-05-20 16:20:40 UTC
Parallelism
74/100
Blocked
47%
Avg conflicts / tx
1.16
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #75,863,422 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w08w09w110w211w312w414w015w116w217w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0018
0x1b6862…e19c
10 touches
10 conflicts
0xcb45d9d6…cb80
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0x6a04329c…9efe
0xd32edf…ff58
9 touches
10 conflicts
0x941a33ca…2f92
0xd18b7e…414b
6 touches
3 conflicts
0xf26eda05…0203
0xd18b7e…414b
6 touches
3 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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity