pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,244,862
← previous block
next block →
recent activity
Analyzing
Block #95,244,862
6 transactions · 6 stateful · 2026-08-12 03:52:25 UTC
Parallelism
67
/100
Blocked
17
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,244,862
· 6 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
#2
0x3f5c179b
· blocks 1
#4
execFwdPositionOps
#5
updateDataFeedsValuesPartial
#3
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0004
0x4a34c9…b922
4 touches
1 conflict
0x6676e87f…b88f
0x2a68ba…90c5
4 touches
1 conflict
0xdaf4f143…58d4
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x447d2e…e9f5
4 touches
1 conflict
0xb02db393…8fdf
0x447d2e…e9f5
3 touches
1 conflict
0x02cdc23d…55ab
0x447d2e…e9f5
3 touches
1 conflict
0x13fff692…4c39
0x447d2e…e9f5
3 touches
1 conflict
0x3f7706db…f312
0x447d2e…e9f5
3 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:
0x4a34c959…66b922
1 conflict on slot
0x0000000000…000004
Audit this contract →
← previous block
·
next block →
recent activity