← previous blocknext block →recent activity
Analyzing
Block #76,233,056
21 transactions · 19 stateful · 2026-05-22 09:22:46 UTC
Parallelism
81/100
Blocked
53%
Avg conflicts / tx
0.62
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #76,233,056 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w07w28w19w010w111w216w017w118w219w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7cee1be1…e770
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xab3526…fa38
6 touches
3 conflicts
0xe5e7089a…fb91
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xcce2fd99…a8eb
0x3bd359…433a
4 touches
1 conflict
0xd77e90ec…8c04
0x3bd359…433a
4 touches
1 conflict
0xdd70bea3…1ffe
0x3bd359…433a
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: Perpl
3 conflicts on slot 0x7cee1be1f4…b4e770
Audit this contract →
← previous block·next block →recent activity