← previous blocknext block →recent activity
Analyzing
Block #76,436,350
13 transactions · 11 stateful · 2026-05-23 07:56:09 UTC
Parallelism
77/100
Blocked
27%
Avg conflicts / tx
0.46
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,436,350 · 13 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
1w03w14w06w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x65ef6e8c…d10d
0xa6afd3…d132
6 touches
3 conflicts
0xda693078…02d1
0xa6afd3…d132
5 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x24781048…4772
0x2a68ba…90c5
2 touches
0 conflicts
0x00f245ce…1e10
0x34b655…2a6f
2 touches
0 conflicts
0x067a7fb3…3966
0x34b655…2a6f
2 touches
0 conflicts
0x0a69823e…9cc9
0x34b655…2a6f
2 touches
0 conflicts
0x102d8a53…4bd8
0x34b655…2a6f
2 touches
0 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: 0xa6afd386…b0d132
3 conflicts on slot 0x65ef6e8c80…e2d10d
Audit this contract →
← previous block·next block →recent activity