← previous blocknext block →recent activity
Analyzing
Block #96,619,696
41 transactions · 25 stateful · 2026-08-16 23:21:56 UTC
Parallelism
88/100
Blocked
44%
Avg conflicts / tx
0.61
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,619,696 · 41 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
2w09w010w111w213w314w418w123w024w126w227w028w129w334w135w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x103de0…bb55
10 touches
10 conflicts
0xb9eeba47…a313
0xd32edf…ff58
9 touches
10 conflicts
0x2886e2bc…6ab8
0x065c9d…c394
6 touches
3 conflicts
0x731e6d82…2883
0x065c9d…c394
4 touches
1 conflict
0x342fbbca…d443
0x40c49f…2af0
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xea02471d…1539
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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: 0x103de0b5…25bb55
10 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity