← previous blocknext block →recent activity
Analyzing
Block #96,489,059
14 transactions · 14 stateful · 2026-08-16 12:24:35 UTC
Parallelism
64/100
Blocked
43%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,489,059 · 14 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
2w03w14w25w38w09w110w211w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe504ee67…1ddb
0x968279…9342
6 touches
3 conflicts
0x00000000…0006
0x968279…9342
6 touches
3 conflicts
0xe0bd8e39…1218
0x968279…9342
6 touches
3 conflicts
0xe0bd8e39…1219
0x968279…9342
6 touches
3 conflicts
0xe0bd8e39…121c
0x968279…9342
6 touches
3 conflicts
0xe0bd8e39…121d
0x968279…9342
6 touches
3 conflicts
0xe0bd8e39…121f
0x968279…9342
6 touches
3 conflicts
0xe504ee67…1dd8
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 0xe504ee671e…781ddb
Audit this contract →
← previous block·next block →recent activity