← previous blocknext block →recent activity
Analyzing
Block #96,665,524
23 transactions · 22 stateful · 2026-08-17 03:12:25 UTC
Parallelism
70/100
Blocked
41%
Avg conflicts / tx
1.26
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,665,524 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w06w18w011w312w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf1345bef…5530
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x4fe65078…76b9
0x34b655…2a6f
14 touches
21 conflicts
0x86cea35b…bdff
0x34b655…2a6f
8 touches
6 conflicts
0x38c6ff01…689f
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
8 touches
6 conflicts
0xbec23443…9293
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 0xf1345befeb…1b5530
Audit this contract →
← previous block·next block →recent activity