← previous blocknext block →recent activity
Analyzing
Block #76,436,448
18 transactions · 18 stateful · 2026-05-23 07:56:48 UTC
Parallelism
56/100
Blocked
50%
Avg conflicts / tx
1.67
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #76,436,448 · 18 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w58w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
12 touches
15 conflicts
0xd12056d1…cf73
0x34b655…2a6f
8 touches
6 conflicts
0x1c913164…5c2e
0x34b655…2a6f
8 touches
6 conflicts
0x88915805…fbc9
0x34b655…2a6f
6 touches
3 conflicts
0x908d4442…2c4b
0x34b655…2a6f
6 touches
3 conflicts
0xaa3492db…3703
0x34b655…2a6f
6 touches
3 conflicts
0xaef9058e…322a
0x34b655…2a6f
6 touches
3 conflicts
0xbf2405ea…0ed6
0x34b655…2a6f
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
15 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity