← previous blocknext block →recent activity
Analyzing
Block #76,346,863
15 transactions · 11 stateful · 2026-05-22 22:00:03 UTC
Parallelism
80/100
Blocked
36%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,346,863 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w17w08w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x908d4442…2c4b
0x34b655…2a6f
4 touches
1 conflict
0xc6417de0…2191
0xc8689a…ee79
4 touches
1 conflict
0x75d17fe1…81a4
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xe54a1f6f…18f2
0x34b655…2a6f
4 touches
1 conflict
0x99f080dc…58c1
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x12bc0d2c…1c12
0x34b655…2a6f
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
1 conflict on slot 0x908d4442aa…222c4b
Audit this contract →
← previous block·next block →recent activity