← previous blocknext block →recent activity
Analyzing
Block #95,349,821
14 transactions · 12 stateful · 2026-08-12 12:50:29 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,349,821 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w07w18w09w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb1d30b59…529f
0x34b655…2a6f
8 touches
6 conflicts
0xb39cb1d8…effa
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x92be05b8…60ee
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xbec23443…9293
0x34b655…2a6f
6 touches
3 conflicts
0x5bbda264…7dd0
0x34b655…2a6f
4 touches
1 conflict
0x5bbda264…7dd1
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 0xb1d30b592c…d5529f
Audit this contract →
← previous block·next block →recent activity