← previous blocknext block →recent activity
Analyzing
Block #95,569,296
7 transactions · 6 stateful · 2026-08-13 07:16:52 UTC
Parallelism
43/100
Blocked
50%
Avg conflicts / tx
0.86
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,569,296 · 7 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
1w02w13w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x95c47f03…f1bb
0x34b655…2a6f
8 touches
6 conflicts
0x2717d69b…b6f2
0x34b655…2a6f
4 touches
1 conflict
0x12348fc7…e86b
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0x19d0eecc…6863
0x34b655…2a6f
2 touches
0 conflicts
0x6bf4acb7…93da
0x34b655…2a6f
2 touches
0 conflicts
0x70e3da66…674a
0x34b655…2a6f
2 touches
0 conflicts
0x775a8ad3…8307
0x34b655…2a6f
2 touches
0 conflicts
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