← previous blocknext block →recent activity
Analyzing
Block #96,603,759
20 transactions · 18 stateful · 2026-08-16 22:01:46 UTC
Parallelism
70/100
Blocked
44%
Avg conflicts / tx
1.45
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,603,759 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w17w08w19w210w311w412w415w519w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a157e0…215b
0x34b655…2a6f
12 touches
15 conflicts
0x8a5ced1c…3b29
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x7de57974…f5ba
0x34b655…2a6f
6 touches
3 conflicts
0x5b0ed476…61a6
0x34b655…2a6f
6 touches
3 conflicts
0x3e6302c8…64f5
0x34b655…2a6f
4 touches
1 conflict
0x0bd95eb4…e562
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 0x13a157e0c8…ea215b
Audit this contract →
← previous block·next block →recent activity