pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#112,083,215
← previous block
next block →
recent activity
Analyzing
Block #112,083,215
15 transactions · 12 stateful · 2026-10-10 04:09:23 UTC
Parallelism
87
/100
Blocked
8
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#112,083,215
· 15 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x00040000
#2
0x0000261d
#3
0x59558d29
#4
0xab083028
#5
execOrders
#6
execOrders
· blocks 1
#7
execOrders
#9
0x5acec890
#10
0x5acec890
#11
execFwdPositionOpsV2
#12
execFwdPositionOpsV2
#13
setData
#14
0x0c7abd22
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xaad6be10…0801
0x2a68ba…90c5
2 touches
0 conflicts
0xcc69885f…792f
0x30a88b…7102
2 touches
0 conflicts
0xd5d6c8dc…8045
0x30a88b…7102
2 touches
0 conflicts
0xd9d16d34…330f
0x30a88b…7102
2 touches
0 conflicts
0xdc686ec4…237e
0x30a88b…7102
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:
Perpl
1 conflict on slot
0xbde524f475…b143bf
Audit this contract →
← previous block
·
next block →
recent activity