← previous blocknext block →recent activity
Analyzing
Block #96,147,596
13 transactions · 13 stateful · 2026-08-15 07:47:11 UTC
Parallelism
85/100
Blocked
31%
Avg conflicts / tx
0.31
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,147,596 · 13 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
1w02w14w07w08w19w010w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf97ac78e…6b7f
0x968279…9342
4 touches
1 conflict
0x0a746e83…cef5
0x968279…9342
4 touches
1 conflict
0x0a746e83…cef7
0x968279…9342
4 touches
1 conflict
0xf97ac78e…6b78
0x968279…9342
4 touches
1 conflict
0xf97ac78e…6b79
0x968279…9342
4 touches
1 conflict
0xf97ac78e…6b7c
0x968279…9342
4 touches
1 conflict
0xf97ac78e…6b7d
0x968279…9342
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: 0x96827978…f09342
1 conflict on slot 0xf97ac78e5c…4b6b7f
Audit this contract →
← previous block·next block →recent activity