← previous blocknext block →recent activity
Analyzing
Block #95,471,813
30 transactions · 24 stateful · 2026-08-12 23:06:34 UTC
Parallelism
77/100
Blocked
46%
Avg conflicts / tx
1.1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #95,471,813 · 30 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w07w09w010w111w212w313w114w015w116w217w319w422w528w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53f393fa…00b9
0x34b655…2a6f
14 touches
21 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5142ff3f…6c11
0x34b655…2a6f
4 touches
1 conflict
0x770870e2…a2a0
0x34b655…2a6f
4 touches
1 conflict
0x7a606d8a…9700
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
21 conflicts on slot 0x53f393fafd…2a00b9
Audit this contract →
← previous block·next block →recent activity