← previous blocknext block →recent activity
Analyzing
Block #95,528,135
15 transactions · 13 stateful · 2026-08-13 03:49:51 UTC
Parallelism
67/100
Blocked
46%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,528,135 · 15 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
1w02w03w14w26w17w38w49w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeb83d3c0…9cf5
0x34b655…2a6f
6 touches
3 conflicts
0x08636046…e60f
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x8cd684d0…c3cb
0x34b655…2a6f
4 touches
1 conflict
0x11b69a7e…334e
0xee8c0e…1242
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
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 0xeb83d3c0c3…f09cf5
Audit this contract →
← previous block·next block →recent activity