← previous blocknext block →recent activity
Analyzing
Block #95,086,868
19 transactions · 19 stateful · 2026-08-11 14:36:45 UTC
Parallelism
63/100
Blocked
47%
Avg conflicts / tx
0.63
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #95,086,868 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w36w49w511w012w615w116w118w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x50afedcd…91cc
0x34b655…2a6f
8 touches
6 conflicts
0xf219f7cf…7379
0xa6afd3…d132
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xbfca3cd0…5023
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xf5ea108a…dbf6
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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 0x50afedcd15…9a91cc
Audit this contract →
← previous block·next block →recent activity