← previous blocknext block →recent activity
Analyzing
Block #76,196,977
8 transactions · 6 stateful · 2026-05-22 05:22:10 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,196,977 · 8 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
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x80630fb9…a436
0x34b655…2a6f
4 touches
1 conflict
0xb6bc6efb…ad9b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x017130f6…f21c
0x2ab50b…5c41
2 touches
0 conflicts
0x0aae760d…1092
0x2ab50b…5c41
2 touches
0 conflicts
0x16b29e68…b662
0x2ab50b…5c41
2 touches
0 conflicts
0x16f4f8ab…a97d
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 0x80630fb921…6ea436
Audit this contract →
← previous block·next block →recent activity