← previous blocknext block →recent activity
Analyzing
Block #95,565,090
13 transactions · 13 stateful · 2026-08-13 06:55:43 UTC
Parallelism
62/100
Blocked
38%
Avg conflicts / tx
0.38
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,565,090 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w27w38w49w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa9a9d0e0…4087
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xbed66fbf…6810
0x34b655…2a6f
4 touches
1 conflict
0xdcae00a6…c017
0x34b655…2a6f
4 touches
1 conflict
0x2840c278…bbc7
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x30ae635d…5e67
0x34b655…2a6f
4 touches
1 conflict
0x6e389ca9…17e8
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
1 conflict on slot 0xa9a9d0e00e…304087
Audit this contract →
← previous block·next block →recent activity