← previous blocknext block →recent activity
Analyzing
Block #95,549,298
10 transactions · 9 stateful · 2026-08-13 05:36:18 UTC
Parallelism
50/100
Blocked
44%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,549,298 · 10 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
2w04w15w26w39w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x39146670…bc53
0x34b655…2a6f
6 touches
3 conflicts
0xf346808d…6ad4
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad07
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad15
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x28d9aaeb…ef07
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
3 conflicts on slot 0x3914667037…e5bc53
Audit this contract →
← previous block·next block →recent activity