← previous blocknext block →recent activity
Analyzing
Block #95,915,304
15 transactions · 13 stateful · 2026-08-14 12:18:30 UTC
Parallelism
87/100
Blocked
23%
Avg conflicts / tx
0.27
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,915,304 · 15 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
1w02w03w08w09w111w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfb378fb4…bb46
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x4acbdbcf…a8c6
0x34b655…2a6f
4 touches
1 conflict
0x1803586e…d149
0xa6afd3…d132
4 touches
1 conflict
0xa3a621f8…75a2
0x34b655…2a6f
4 touches
1 conflict
0xd76a03c0…e690
0x34b655…2a6f
4 touches
1 conflict
0xe6997d36…4f33
0x34b655…2a6f
4 touches
1 conflict
0xb05cd4f5…73d0
0x2b46c0…1669
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 0xfb378fb45a…5abb46
Audit this contract →
← previous block·next block →recent activity