pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#112,612,925
← previous block
next block →
recent activity
Analyzing
Block #112,612,925
10 transactions · 10 stateful · 2026-10-12 00:34:26 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#112,612,925
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x59558d29
#2
0x928e4afa
#3
execOrders
#4
0x0c7abd22
#5
execFwdPositionOpsV2
#6
0x3f5c179b
#7
0x57368ddf
#8
setData
· blocks 1
#9
setData
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00af3be9…4301
0x34b655…2a6f
2 touches
0 conflicts
0x02b40964…6885
0x34b655…2a6f
2 touches
0 conflicts
0x1c385c8c…a0fb
0x34b655…2a6f
2 touches
0 conflicts
0x1fefee3b…1670
0x34b655…2a6f
2 touches
0 conflicts
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:
0x33176be2…ede078
1 conflict on slot
0x09106a952c…111467
Audit this contract →
← previous block
·
next block →
recent activity