← previous blocknext block →recent activity
Analyzing
Block #96,121,449
13 transactions · 12 stateful · 2026-08-15 05:35:36 UTC
Parallelism
54/100
Blocked
58%
Avg conflicts / tx
1.08
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,121,449 · 13 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
2w03w14w25w36w47w59w412w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13fa8d63…ba0d
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xea1b8c07…b969
0x34b655…2a6f
4 touches
1 conflict
0xa5a8ffca…8de2
0x34b655…2a6f
4 touches
1 conflict
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0x08e8f2c9…a11a
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
10 conflicts on slot 0x13fa8d637b…d7ba0d
Audit this contract →
← previous block·next block →recent activity