← previous blocknext block →recent activity
Analyzing
Block #95,073,608
62 transactions · 61 stateful · 2026-08-11 13:30:02 UTC
Parallelism
95/100
Blocked
5%
Avg conflicts / tx
0.06
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,073,608 · 62 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w06w161w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e17e5be…d212
0x34b655…2a6f
6 touches
3 conflicts
0x2b5101ac…090b
0x34b655…2a6f
6 touches
3 conflicts
0x9aaca373…d7c0
0x34b655…2a6f
4 touches
1 conflict
0xe63cb2d0…c66f
0x34b655…2a6f
4 touches
1 conflict
0xb06e151a…b159
0x065c9d…c394
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x11258774…9892
0x2a68ba…90c5
4 touches
1 conflict
0x3439dfbc…0d03
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
3 conflicts on slot 0x5e17e5be17…c5d212
Audit this contract →
← previous block·next block →recent activity