← previous blocknext block →recent activity
Analyzing
Block #95,478,833
25 transactions · 24 stateful · 2026-08-12 23:41:53 UTC
Parallelism
76/100
Blocked
46%
Avg conflicts / tx
0.84
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,478,833 · 25 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
1w05w06w17w28w39w411w112w013w118w119w020w121w223w224w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4cabb80a…46bf
0x34b655…2a6f
8 touches
6 conflicts
0xec7d120d…7084
0x34b655…2a6f
8 touches
6 conflicts
0xb33ff823…1188
0x065c9d…c394
6 touches
3 conflicts
0xf5ea108a…dbf6
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x53f393fa…00b9
0x34b655…2a6f
4 touches
1 conflict
0x691bdabc…c1b4
0x34b655…2a6f
4 touches
1 conflict
0x6a10a152…a08f
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 0x4cabb80a0e…7546bf
Audit this contract →
← previous block·next block →recent activity