← previous blocknext block →recent activity
Analyzing
Block #95,473,084
16 transactions · 16 stateful · 2026-08-12 23:12:58 UTC
Parallelism
69/100
Blocked
56%
Avg conflicts / tx
1.13
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,473,084 · 16 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
1w02w13w04w16w17w28w29w311w412w013w115w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x620b761c…270e
0x34b655…2a6f
8 touches
6 conflicts
0xe2ca9bf2…8da8
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x81ca8c9e…28cb
0x34b655…2a6f
6 touches
3 conflicts
0x398c0e99…196a
0x34b655…2a6f
6 touches
3 conflicts
0xa3a621f8…75a2
0x34b655…2a6f
6 touches
3 conflicts
0x7b481037…3457
0x34b655…2a6f
4 touches
1 conflict
0x7da6eb60…b34e
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 0x620b761c50…c2270e
Audit this contract →
← previous block·next block →recent activity