← previous blocknext block →recent activity
Analyzing
Block #76,195,182
15 transactions · 15 stateful · 2026-05-22 05:10:14 UTC
Parallelism
67/100
Blocked
60%
Avg conflicts / tx
1.2
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #76,195,182 · 15 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
1w02w13w25w26w27w08w111w112w213w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9fc6ea79…e2dc
0x34b655…2a6f
8 touches
6 conflicts
0xae6a4c09…c78a
0x34b655…2a6f
8 touches
6 conflicts
0x90e14f35…24e2
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…002e
0x1b6862…e19c
6 touches
3 conflicts
0x93afca4c…b47e
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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
6 conflicts on slot 0x9fc6ea791d…ace2dc
Audit this contract →
← previous block·next block →recent activity