← previous blocknext block →recent activity
Analyzing
Block #96,017,451
17 transactions · 14 stateful · 2026-08-14 20:52:30 UTC
Parallelism
71/100
Blocked
43%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,017,451 · 17 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
1w02w17w08w19w210w311w414w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0031
0x59df86…2780
10 touches
10 conflicts
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0002
0x103de0…bb55
2 touches
0 conflicts
0x00000000…0003
0x103de0…bb55
2 touches
0 conflicts
0x00000000…0005
0x103de0…bb55
2 touches
0 conflicts
0x213ee207…a151
0x2b46c0…1669
2 touches
0 conflicts
0x46279ae7…20dd
0x2b46c0…1669
2 touches
0 conflicts
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: 0x59df8637…6d2780
10 conflicts on slot 0x0000000000…000031
Audit this contract →
← previous block·next block →recent activity