pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#106,028,144
← previous block
next block →
recent activity
Analyzing
Block #106,028,144
13 transactions · 12 stateful · 2026-09-18 23:58:42 UTC
Parallelism
85
/100
Blocked
17
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#106,028,144
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x4ccf0801
· blocks 1
#2
matchOrders
#3
0xab083028
· blocks 1
#5
execOrders
#6
0x928e4afa
#7
updateDataFeedsValuesPartial
#9
0x59558d29
#10
execFwdPositionOpsV2
#11
setData
#12
execOrders
#4
0xab083028
#8
0x4cb2db39
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w0
4
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…004f
0x80c745…7210
4 touches
1 conflict
0x00000000…0050
0x80c745…7210
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x2825c4f2…f77f
0x01bff4…1071
2 touches
0 conflicts
0x7ab0b5f5…39e2
0x01bff4…1071
2 touches
0 conflicts
0x4213f1c0…219a
0x2a68ba…90c5
2 touches
0 conflicts
0xebc2e0d7…958e
0x3bd359…433a
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:
0x80c74517…647210
1 conflict on slot
0x0000000000…00004f
Audit this contract →
← previous block
·
next block →
recent activity