← previous blocknext block →recent activity
Analyzing
Block #95,115,602
19 transactions · 15 stateful · 2026-08-11 17:01:18 UTC
Parallelism
74/100
Blocked
47%
Avg conflicts / tx
0.68
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,115,602 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w06w17w28w39w415w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2655625d…b058
0x34b655…2a6f
8 touches
6 conflicts
0xacd1b162…bee6
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x93aa1b2e…8459
0x34b655…2a6f
6 touches
3 conflicts
0xf0e5a298…4827
0x34b655…2a6f
6 touches
3 conflicts
0x80398c66…f3cc
0x34b655…2a6f
4 touches
1 conflict
0x948836ff…59ab
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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
6 conflicts on slot 0x2655625d49…fcb058
Audit this contract →
← previous block·next block →recent activity