← previous blocknext block →recent activity
Analyzing
Block #76,284,350
12 transactions · 8 stateful · 2026-05-22 15:03:57 UTC
Parallelism
83/100
Blocked
25%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,284,350 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w08w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf9b8ae99…32b3
0x34b655…2a6f
4 touches
1 conflict
0xf9b8ae99…32b4
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xf722d24e…ac24
0x34b655…2a6f
4 touches
1 conflict
0x5dee2ee4…7362
0x1efe02…37d6
2 touches
0 conflicts
0xb772de34…3f49
0x1efe02…37d6
2 touches
0 conflicts
0x00bac013…a28c
0x91b81b…6d56
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: Perpl
1 conflict on slot 0xf9b8ae99dc…3532b3
Audit this contract →
← previous block·next block →recent activity