← previous blocknext block →recent activity
Analyzing
Block #76,222,813
10 transactions · 7 stateful · 2026-05-22 08:14:10 UTC
Parallelism
80/100
Blocked
14%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,222,813 · 10 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
2w06w1
- 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
0x00000000…0006
0x2ab50b…5c41
2 touches
0 conflicts
0x017130f6…f21c
0x2ab50b…5c41
2 touches
0 conflicts
0x05c2bffb…8cd2
0x2ab50b…5c41
2 touches
0 conflicts
0x113dc775…ab67
0x2ab50b…5c41
2 touches
0 conflicts
0x146ab97f…fe43
0x2ab50b…5c41
2 touches
0 conflicts
0x16b29e68…b662
0x2ab50b…5c41
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