← previous blocknext block →recent activity
Analyzing
Block #95,565,943
19 transactions · 18 stateful · 2026-08-13 07:00:01 UTC
Parallelism
74/100
Blocked
33%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,565,943 · 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
1w02w13w24w25w37w418w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x95c47f03…f1bb
0x34b655…2a6f
8 touches
6 conflicts
0x2840c278…bbc7
0x34b655…2a6f
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0x5e78c401…7a7e
0x34b655…2a6f
4 touches
1 conflict
0x78860c4f…cade
0x34b655…2a6f
4 touches
1 conflict
0x312e7bb3…b9b4
0x34b655…2a6f
4 touches
1 conflict
0x35649443…8b45
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
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 0x95c47f0322…51f1bb
Audit this contract →
← previous block·next block →recent activity