← previous blocknext block →recent activity
Analyzing
Block #96,784,191
12 transactions · 11 stateful · 2026-08-17 13:09:16 UTC
Parallelism
67/100
Blocked
36%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,784,191 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w28w39w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb018712d…66f6
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x3cd30154…5939
0x34b655…2a6f
4 touches
1 conflict
0x4c511cd0…0919
0x34b655…2a6f
4 touches
1 conflict
0x5d3ca7b1…bb8c
0x34b655…2a6f
4 touches
1 conflict
0x61e7b277…fee7
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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: Perpl
3 conflicts on slot 0xb018712d0b…9366f6
Audit this contract →
← previous block·next block →recent activity