← previous blocknext block →recent activity
Analyzing
Block #95,113,589
14 transactions · 13 stateful · 2026-08-11 16:51:11 UTC
Parallelism
86/100
Blocked
8%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,113,589 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa56e54d0…2d39
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1b5d2e60…99b5
0x34b655…2a6f
2 touches
0 conflicts
0x5f453c44…fa94
0x34b655…2a6f
2 touches
0 conflicts
0x6603ed8d…cde2
0x34b655…2a6f
2 touches
0 conflicts
0x681dd2e1…ce40
0x34b655…2a6f
2 touches
0 conflicts
0x6b86b520…b4b9
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0xa56e54d018…f82d39
Audit this contract →
← previous block·next block →recent activity