pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,264,778
← previous block
next block →
recent activity
Analyzing
Block #98,264,778
36 transactions · 28 stateful · 2026-08-22 18:31:06 UTC
Parallelism
83
/100
Blocked
50
%
Avg conflicts / tx
0.75
Longest chain
6
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,264,778
· 36 txs across 6 waves · depth 6
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
#0
syscallReward
#1
0xd524a9da
· blocks 3
#2
executePacked
#3
0x4ccf0801
· blocks 1
#4
0x7b84f330
· blocks 1
#5
0x50a0b275
#8
main_all
#9
main_all
#10
execOrders
· blocks 2
#11
0x6ad2e98b
#12
execOrders
· blocks 2
#15
0x59558d29
#16
execPerpOps
· blocks 1
#18
0xe3a3c9cc
#19
0x5acec890
· blocks 2
#21
0x62be7533
#22
0x3f5c179b
#23
execFwdPositionOpsV2
· blocks 1
#25
updateTemporalNumericValuesV1
#27
0xed82b078
#29
execFwdPositionOpsV2
#30
setData
#6
0x41a8f47c
· blocks 3
#13
execOrders
#14
0x4cb2db39
#17
execPerpOps
#20
0x928e4afa
· blocks 3
#26
execFwdPositionOpsV2
· blocks 1
#35
0x7b84f330
#7
0x41a8f47c
#24
0xed82b078
· blocks 1
#31
execOrders
· blocks 3
#28
0xed82b078
#32
execOrders
· blocks 2
#33
execOrders
· blocks 1
#34
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w0
4
w0
6
w1
7
w2
10
w0
12
w0
13
w1
14
w1
16
w0
17
w1
19
w0
20
w1
23
w0
24
w2
26
w1
28
w3
31
w2
32
w3
33
w4
34
w5
35
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xb5cddf91…0abf
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x7aad02c6…b979
0x34b655…2a6f
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
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:
Perpl
6 conflicts on slot
0xe5bb3628b5…71e5f1
Audit this contract →
← previous block
·
next block →
recent activity