← previous blocknext block →recent activity
Analyzing
Block #95,655,158
20 transactions · 18 stateful · 2026-08-13 14:28:46 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
0.55
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,655,158 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w17w214w017w318w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe3471350…0bcf
0x34b655…2a6f
8 touches
6 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x170e4e4c…2b90
0x34b655…2a6f
4 touches
1 conflict
0x19cbeea8…ecf3
0x34b655…2a6f
4 touches
1 conflict
0x2f0e1e70…649b
0x34b655…2a6f
4 touches
1 conflict
0x37d7b588…0e99
0x34b655…2a6f
4 touches
1 conflict
0x3b8b2dfb…8ffe
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 0xe347135026…5b0bcf
Audit this contract →
← previous block·next block →recent activity