← previous blocknext block →recent activity
Analyzing
Block #95,375,139
25 transactions · 22 stateful · 2026-08-12 14:58:49 UTC
Parallelism
80/100
Blocked
27%
Avg conflicts / tx
0.52
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,375,139 · 25 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
2w08w09w110w212w316w018w019w123w124w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x44a2c3ff…0abc
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xcf17589f…048c
0x34b655…2a6f
6 touches
3 conflicts
0x160f117d…8e90
0x065c9d…c394
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x00ddbbf2…4588
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xcb165620…1189
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 0x44a2c3ff07…e10abc
Audit this contract →
← previous block·next block →recent activity