pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,917,899
← previous block
next block →
recent activity
Analyzing
Block #100,917,899
36 transactions · 28 stateful · 2026-09-01 02:03:13 UTC
Parallelism
81
/100
Blocked
57
%
Avg conflicts / tx
1
Longest chain
7
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,917,899
· 36 txs across 7 waves · depth 7
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
wave
w6
#0
syscallReward
#1
0x4f819052
· blocks 4
#2
0xcf7468f4
#4
0xd524a9da
#5
0x6a9632d9
#6
matchOrders
#7
0x0c7abd22
· blocks 3
#11
0x4297b034
#13
0x8263f5d9
#14
0x8263f5d9
#15
execOrder
#16
0x5acec890
· blocks 3
#19
execPerpOps
#20
execPerpOps
#21
updateDataFeedsValuesPartial
#24
execPerpOps
#29
0x3f5c179b
#30
0x3f5c179b
· blocks 1
#33
0x6a9632d9
#34
setData
#3
0xab083028
· blocks 3
#8
0x0c7abd22
· blocks 2
#17
0x5acec890
· blocks 7
#35
0xc7068c7b
#9
0x0c7abd22
· blocks 1
#12
0xab083028
· blocks 2
#18
0x5acec890
· blocks 1
#22
execOrders
#23
execOrders
· blocks 2
#10
0x0c7abd22
#25
0xe3a3c9cc
· blocks 1
#26
execFwdPositionOpsV2
· blocks 3
#27
0x62be7533
#28
execFwdPositionOpsV2
· blocks 2
#31
execFwdPositionOpsV2
· blocks 1
#32
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
7
w0
8
w1
9
w2
10
w3
12
w2
16
w0
17
w1
18
w2
22
w2
23
w2
25
w3
26
w3
27
w4
28
w4
31
w5
32
w6
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x4a07563d…4223
0xd32edf…ff58
7 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x327c57dd…836d
0x34b655…2a6f
6 touches
3 conflicts
0xe7b20cb4…a869
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 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:
Kuru Exchange: MarginAccount
10 conflicts on slot
0xaad6be10ae…2c0801
Audit this contract →
← previous block
·
next block →
recent activity