← previous blocknext block →recent activity
Analyzing
Block #96,709,179
13 transactions · 13 stateful · 2026-08-17 06:51:59 UTC
Parallelism
46/100
Blocked
46%
Avg conflicts / tx
1.54
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,709,179 · 13 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w36w47w510w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8cd684d0…c3cb
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xe2267a44…fb98
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0xa9a9d0e0…4087
0x34b655…2a6f
6 touches
3 conflicts
0x39fc983b…2a6f
0x34b655…2a6f
5 touches
3 conflicts
0x966e45cf…0f25
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
15 conflicts on slot 0x8cd684d0d7…f5c3cb
Audit this contract →
← previous block·next block →recent activity