← previous blocknext block →recent activity
Analyzing
Block #76,526,382
21 transactions · 17 stateful · 2026-05-23 17:55:34 UTC
Parallelism
76/100
Blocked
41%
Avg conflicts / tx
0.76
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #76,526,382 · 21 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
5w08w19w011w013w214w317w118w219w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c913164…5c2e
0x34b655…2a6f
8 touches
6 conflicts
0xf853eb8e…4027
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xe34b767d…24d7
0xd32edf…ff58
7 touches
6 conflicts
0x55b6a001…1e7a
0x34b655…2a6f
6 touches
3 conflicts
0x7cbd466f…1700
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb85
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 0x1c913164f5…845c2e
Audit this contract →
← previous block·next block →recent activity