← previous blocknext block →recent activity
Analyzing
Block #96,256,949
15 transactions · 12 stateful · 2026-08-15 16:57:10 UTC
Parallelism
87/100
Blocked
33%
Avg conflicts / tx
0.27
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,256,949 · 15 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w07w08w110w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf6d261c4…ede3
0x968279…9342
4 touches
1 conflict
0xb7be3cda…5ee8
0x968279…9342
4 touches
1 conflict
0xf6d261c4…ede0
0x968279…9342
4 touches
1 conflict
0xf6d261c4…ede1
0x968279…9342
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x4b76146e…0dcb
0x34b655…2a6f
4 touches
1 conflict
0x81561f70…fefd
0x34b655…2a6f
4 touches
1 conflict
0xa5a8ffca…8de2
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: 0x96827978…f09342
1 conflict on slot 0xf6d261c461…fcede3
Audit this contract →
← previous block·next block →recent activity