← previous blocknext block →recent activity
Analyzing
Block #95,268,685
16 transactions · 12 stateful · 2026-08-12 06:00:03 UTC
Parallelism
88/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,268,685 · 16 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
1w09w111w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9fd37234…2731
0x34b655…2a6f
4 touches
1 conflict
0x57330c5d…9973
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xff8b4178…773d
0x34b655…2a6f
4 touches
1 conflict
0x6676e87f…b88f
0x2a68ba…90c5
2 touches
0 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
2 touches
0 conflicts
0xe5bb3628…e5e8
0x34b655…2a6f
2 touches
0 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
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 0x9fd37234c4…602731
Audit this contract →
← previous block·next block →recent activity