← previous blocknext block →recent activity
Analyzing
Block #95,580,575
14 transactions · 13 stateful · 2026-08-13 08:13:36 UTC
Parallelism
64/100
Blocked
46%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,580,575 · 14 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
2w03w04w15w26w39w310w412w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x6ab46c0d…930f
0x34b655…2a6f
5 touches
3 conflicts
0xce06a0f7…efef
0x34b655…2a6f
5 touches
3 conflicts
0x989252a1…d812
0xa6afd3…d132
4 touches
1 conflict
0x2328941c…84d3
0x34b655…2a6f
4 touches
1 conflict
0x8925be8e…4b81
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
6 conflicts on slot 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity