← previous blocknext block →recent activity
Analyzing
Block #76,113,430
18 transactions · 17 stateful · 2026-05-21 20:05:51 UTC
Parallelism
83/100
Blocked
41%
Avg conflicts / tx
0.72
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,113,430 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w27w08w19w210w011w114w015w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7982ca1b…f8da
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0xd90a2b35…18e9
0xd32edf…ff58
5 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x22863bf9…19df
0x34b655…2a6f
4 touches
1 conflict
0x391a3995…1483
0x34b655…2a6f
4 touches
1 conflict
0x6f6fc26c…3e34
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
3 conflicts on slot 0x7982ca1bf4…13f8da
Audit this contract →
← previous block·next block →recent activity