← previous blocknext block →recent activity
Analyzing
Block #95,473,602
12 transactions · 11 stateful · 2026-08-12 23:15:34 UTC
Parallelism
67/100
Blocked
45%
Avg conflicts / tx
1
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,473,602 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w16w27w08w39w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbd96f96f…5843
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x3e3f27ce…580c
0x34b655…2a6f
4 touches
1 conflict
0x4854b070…fb81
0x34b655…2a6f
4 touches
1 conflict
0x7b481037…3457
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
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 0xbd96f96f0a…875843
Audit this contract →
← previous block·next block →recent activity