← previous blocknext block →recent activity
Analyzing
Block #95,747,264
23 transactions · 19 stateful · 2026-08-13 22:13:04 UTC
Parallelism
83/100
Blocked
47%
Avg conflicts / tx
0.78
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,747,264 · 23 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
1w02w13w25w06w17w110w011w112w013w214w316w017w018w122w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a57a2b8…3cdd
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x95c47f03…f1bb
0x34b655…2a6f
6 touches
3 conflicts
0x39633fd5…c03a
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0002
0xeae24c…0be0
4 touches
1 conflict
0xab360ba6…efc4
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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 0x0a57a2b8cd…773cdd
Audit this contract →
← previous block·next block →recent activity