← previous blocknext block →recent activity
Analyzing
Block #96,785,360
19 transactions · 17 stateful · 2026-08-17 13:15:09 UTC
Parallelism
47/100
Blocked
53%
Avg conflicts / tx
2.32
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #96,785,360 · 19 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w28w39w410w514w615w717w818w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe8eae8a3…bacc
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
12 touches
15 conflicts
0x4e135144…4167
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6426
0x34b655…2a6f
6 touches
3 conflicts
0x935e0525…f741
0x34b655…2a6f
4 touches
1 conflict
0xb409e204…89ac
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
36 conflicts on slot 0xe8eae8a323…64bacc
Audit this contract →
← previous block·next block →recent activity