← previous blocknext block →recent activity
Analyzing
Block #76,570,285
19 transactions · 14 stateful · 2026-05-23 22:48:01 UTC
Parallelism
74/100
Blocked
43%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #76,570,285 · 19 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
1w02w15w06w27w18w19w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x222fc893…acc9
0xa6afd3…d132
6 touches
3 conflicts
0xdfa159d0…1576
0x065c9d…c394
6 touches
3 conflicts
0xcc4f1f14…aa5f
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002e
0x1b6862…e19c
4 touches
1 conflict
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 0x222fc89388…a6acc9
Audit this contract →
← previous block·next block →recent activity