← previous blocknext block →recent activity
Analyzing
Block #95,534,293
16 transactions · 14 stateful · 2026-08-13 04:20:49 UTC
Parallelism
81/100
Blocked
29%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,534,293 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w07w08w110w112w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a57a2b8…3cdd
0x34b655…2a6f
6 touches
3 conflicts
0x320116df…4c43
0x34b655…2a6f
4 touches
1 conflict
0x62380a51…952f
0x34b655…2a6f
4 touches
1 conflict
0x8299fe6c…5752
0x34b655…2a6f
4 touches
1 conflict
0x8727ada9…770d
0x34b655…2a6f
4 touches
1 conflict
0x8727ada9…770e
0x34b655…2a6f
4 touches
1 conflict
0x982900c0…d7a7
0x34b655…2a6f
4 touches
1 conflict
0xcf907a0c…f7da
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 0x0a57a2b8cd…773cdd
Audit this contract →
← previous block·next block →recent activity