← previous blocknext block →recent activity
Analyzing
Block #76,570,284
16 transactions · 8 stateful · 2026-05-23 22:48:01 UTC
Parallelism
88/100
Blocked
25%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,570,284 · 16 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
1w06w08w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf9b8ae99…32b4
0x34b655…2a6f
4 touches
1 conflict
0xcc4f1f14…aa5f
0x065c9d…c394
4 touches
1 conflict
0xf9b8ae99…32b3
0x34b655…2a6f
4 touches
1 conflict
0x1a97a373…4447
0x065c9d…c394
2 touches
0 conflicts
0x339b9b0c…c88d
0x065c9d…c394
2 touches
0 conflicts
0xdaefd54b…6fca
0x065c9d…c394
2 touches
0 conflicts
0x0aa885fa…a3d1
0x2a68ba…90c5
2 touches
0 conflicts
0x2f88a23f…9dc5
0x2a68ba…90c5
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…3532b4
Audit this contract →
← previous block·next block →recent activity