← previous blocknext block →recent activity
Analyzing
Block #96,083,800
20 transactions · 17 stateful · 2026-08-15 02:26:15 UTC
Parallelism
60/100
Blocked
41%
Avg conflicts / tx
1.4
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #96,083,800 · 20 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
1w03w14w25w311w412w513w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0xa5a8ffca…8de2
0x34b655…2a6f
6 touches
3 conflicts
0x44331cd1…15b0
0x34b655…2a6f
6 touches
3 conflicts
0xd5c56995…6d21
0x34b655…2a6f
6 touches
3 conflicts
0x6492aa04…fe5e
0x34b655…2a6f
5 touches
3 conflicts
0x404573cc…6fdc
0x34b655…2a6f
4 touches
1 conflict
0x524f0872…0d12
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
28 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity