← previous blocknext block →recent activity
Analyzing
Block #96,259,136
20 transactions · 18 stateful · 2026-08-15 17:08:10 UTC
Parallelism
75/100
Blocked
39%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,259,136 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w010w011w112w213w314w416w118w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe0659a3f…90d9
0x000000…a032
10 touches
10 conflicts
0x34b1e500…7687
0x754704…b603
10 touches
10 conflicts
0x00000000…000b
0x754704…b603
10 touches
10 conflicts
0x00000000…000f
0x78999c…f371
10 touches
10 conflicts
0x00000000…000b
0x78999c…f371
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xbbb9fa77…d121
0x34b655…2a6f
4 touches
1 conflict
0xd58bcb08…4fb0
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: 0x00000000…7da032
10 conflicts on slot 0xe0659a3f75…9f90d9
Audit this contract →
← previous block·next block →recent activity