← previous blocknext block →recent activity
Analyzing
Block #95,636,370
22 transactions · 21 stateful · 2026-08-13 12:54:15 UTC
Parallelism
82/100
Blocked
38%
Avg conflicts / tx
0.77
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,636,370 · 22 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
1w02w03w14w05w06w17w28w39w010w211w315w116w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08636046…e60f
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0031
0x59df86…2780
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xf9312173…41a7
0x851145…3f07
4 touches
1 conflict
0x0bf2e71c…3846
0x34b655…2a6f
4 touches
1 conflict
0x25e65ccc…c735
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0xefb62c0f…fef8
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 0x08636046fc…69e60f
Audit this contract →
← previous block·next block →recent activity