← previous blocknext block →recent activity
Analyzing
Block #95,711,702
14 transactions · 13 stateful · 2026-08-13 19:14:02 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,711,702 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w17w08w19w211w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x620b761c…270e
0x34b655…2a6f
6 touches
3 conflicts
0xdeb2b322…0f15
0x851145…3f07
4 touches
1 conflict
0x8649e48f…941c
0xc8689a…ee79
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x0a57a2b8…3cdd
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
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
3 conflicts on slot 0x620b761c50…c2270e
Audit this contract →
← previous block·next block →recent activity