← previous blocknext block →recent activity
Analyzing
Block #76,529,277
17 transactions · 16 stateful · 2026-05-23 18:14:48 UTC
Parallelism
88/100
Blocked
31%
Avg conflicts / tx
0.35
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,529,277 · 17 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
1w02w13w05w06w18w09w110w012w115w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xc6417de0…2191
0xc8689a…ee79
4 touches
1 conflict
0xb24a9fb5…f3d7
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xf9b8ae99…32b4
0x34b655…2a6f
4 touches
1 conflict
0xf9b8ae99…32b3
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
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: Perpl
1 conflict on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity