← previous blocknext block →recent activity
Analyzing
Block #96,548,184
18 transactions · 18 stateful · 2026-08-16 17:22:15 UTC
Parallelism
50/100
Blocked
50%
Avg conflicts / tx
1.78
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #96,548,184 · 18 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w47w58w610w717w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08636046…e60f
0x34b655…2a6f
16 touches
28 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xec7d120d…7084
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x4c702894…9f4c
0x34b655…2a6f
4 touches
1 conflict
0x63759c44…7f20
0x34b655…2a6f
4 touches
1 conflict
0x6ac4a9ce…5f63
0x34b655…2a6f
4 touches
1 conflict
0x9e599b87…c270
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 0x08636046fc…69e60f
Audit this contract →
← previous block·next block →recent activity