← previous blocknext block →recent activity
Analyzing
Block #95,710,123
10 transactions · 7 stateful · 2026-08-13 19:06:02 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,710,123 · 10 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
2w03w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xf1345bef…5530
0x34b655…2a6f
4 touches
1 conflict
0x03e2b457…c0b5
0x34b655…2a6f
2 touches
0 conflicts
0x0a59da58…d96e
0x34b655…2a6f
2 touches
0 conflicts
0x25cdca28…e069
0x34b655…2a6f
2 touches
0 conflicts
0x2c375b7a…5878
0x34b655…2a6f
2 touches
0 conflicts
0x47a3d808…bf46
0x34b655…2a6f
2 touches
0 conflicts
0x59a07ac0…728d
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity