← previous blocknext block →recent activity
Analyzing
Block #96,115,266
12 transactions · 12 stateful · 2026-08-15 05:04:30 UTC
Parallelism
75/100
Blocked
33%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,115,266 · 12 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
2w03w05w17w08w19w211w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9fb1c078…8aad
0x968279…9342
6 touches
3 conflicts
0x521a5982…a82a
0x754704…b603
6 touches
3 conflicts
0x00000000…0006
0x968279…9342
6 touches
3 conflicts
0x8a3f145b…2c54
0x968279…9342
6 touches
3 conflicts
0x8a3f145b…2c55
0x968279…9342
6 touches
3 conflicts
0x8a3f145b…2c57
0x968279…9342
6 touches
3 conflicts
0x9fb1c078…8aa7
0x968279…9342
6 touches
3 conflicts
0x9fb1c078…8aa8
0x968279…9342
6 touches
3 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: 0x96827978…f09342
3 conflicts on slot 0x9fb1c078ee…1d8aad
Audit this contract →
← previous block·next block →recent activity