← previous blocknext block →recent activity
Analyzing
Block #96,116,155
16 transactions · 14 stateful · 2026-08-15 05:08:58 UTC
Parallelism
50/100
Blocked
57%
Avg conflicts / tx
1.75
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #96,116,155 · 16 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
1w02w14w15w06w07w28w39w410w511w613w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xff196840…a453
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x9e10b712…1fc2
0x34b655…2a6f
12 touches
15 conflicts
0x6d50e5d1…f983
0x34b655…2a6f
10 touches
10 conflicts
0x72da4494…8b2f
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x7de57974…f5ba
0x34b655…2a6f
6 touches
3 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0xff19684070…f2a453
Audit this contract →
← previous block·next block →recent activity