← previous blocknext block →recent activity
Analyzing
Block #96,567,267
18 transactions · 17 stateful · 2026-08-16 18:58:13 UTC
Parallelism
44/100
Blocked
65%
Avg conflicts / tx
2.33
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #96,567,267 · 18 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w25w36w47w58w615w716w817w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c188934…158e
0x34b655…2a6f
18 touches
36 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
8 touches
6 conflicts
0xaba6578d…bd48
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x99c46e97…c1b2
0x34b655…2a6f
6 touches
3 conflicts
0xc8f4deb0…dcf3
0x34b655…2a6f
6 touches
3 conflicts
0x536588d3…19c5
0x34b655…2a6f
6 touches
3 conflicts
0x43bc2389…898f
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
36 conflicts on slot 0x4c18893450…c5158e
Audit this contract →
← previous block·next block →recent activity