← previous blocknext block →recent activity
Analyzing
Block #95,123,646
16 transactions · 15 stateful · 2026-08-11 17:41:46 UTC
Parallelism
69/100
Blocked
40%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,123,646 · 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
4w05w06w17w29w010w111w213w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0672e4a2…8d1f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x0e43d18d…f7ac
0x34b655…2a6f
4 touches
1 conflict
0x210e0333…9029
0x34b655…2a6f
4 touches
1 conflict
0x2385516f…eca5
0x34b655…2a6f
4 touches
1 conflict
0x24556a78…47e6
0x34b655…2a6f
4 touches
1 conflict
0x266a6b2c…4376
0x34b655…2a6f
4 touches
1 conflict
0x266a6b2c…4377
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 0x0672e4a279…2f8d1f
Audit this contract →
← previous block·next block →recent activity