← previous blocknext block →recent activity
Analyzing
Block #76,306,649
16 transactions · 13 stateful · 2026-05-22 17:32:21 UTC
Parallelism
63/100
Blocked
62%
Avg conflicts / tx
0.75
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #76,306,649 · 16 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
1w02w13w24w05w17w09w112w213w314w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x3e49348b…9445
0x34b655…2a6f
6 touches
3 conflicts
0xecd64d42…55ea
0xd32edf…ff58
5 touches
3 conflicts
0x0a809ce1…7894
0x34b655…2a6f
4 touches
1 conflict
0x2cf96c0a…538a
0x34b655…2a6f
4 touches
1 conflict
0x707a047e…1dc1
0x34b655…2a6f
4 touches
1 conflict
0x7cee1be1…e770
0x34b655…2a6f
4 touches
1 conflict
0x85a88798…f85e
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity