← previous blocknext block →recent activity
Analyzing
Block #96,147,001
14 transactions · 13 stateful · 2026-08-15 07:44:11 UTC
Parallelism
43/100
Blocked
62%
Avg conflicts / tx
2
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #96,147,001 · 14 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w07w18w39w410w511w612w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea1b8c07…b969
0x34b655…2a6f
14 touches
21 conflicts
0xd66696e0…0842
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…641f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x7d7c8caa…dc36
0x34b655…2a6f
9 touches
10 conflicts
0xcffc17bc…3544
0x34b655…2a6f
8 touches
6 conflicts
0x786d66ce…ae70
0x34b655…2a6f
8 touches
6 conflicts
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
21 conflicts on slot 0xea1b8c07ee…d0b969
Audit this contract →
← previous block·next block →recent activity