← previous blocknext block →recent activity
Analyzing
Block #95,748,143
19 transactions · 14 stateful · 2026-08-13 22:17:29 UTC
Parallelism
68/100
Blocked
43%
Avg conflicts / tx
0.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,748,143 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w18w210w311w312w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x966e45cf…0f25
0x34b655…2a6f
8 touches
6 conflicts
0x0d488000…3831
0x34b655…2a6f
6 touches
3 conflicts
0xb5c7c6aa…fdba
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xd16c07ff…1e55
0x34b655…2a6f
4 touches
1 conflict
0x71cc73a0…d523
0x34b655…2a6f
4 touches
1 conflict
0x8cd684d0…c3cb
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
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 0x966e45cf3c…9f0f25
Audit this contract →
← previous block·next block →recent activity