← previous blocknext block →recent activity
Analyzing
Block #95,350,396
19 transactions · 17 stateful · 2026-08-12 12:53:26 UTC
Parallelism
68/100
Blocked
59%
Avg conflicts / tx
0.84
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,350,396 · 19 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
1w02w13w25w06w17w28w29w312w113w314w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x93b6fab0…09d6
0x34b655…2a6f
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0x95c47f03…f1bb
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x89678d1b…463e
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x352c45ab…a8ee
0x851145…3f07
4 touches
1 conflict
0xc545fdad…74de
0x851145…3f07
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 0x93b6fab01a…2d09d6
Audit this contract →
← previous block·next block →recent activity