pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#103,987,920
← previous block
next block →
recent activity
Analyzing
Block #103,987,920
42 transactions · 25 stateful · 2026-09-11 20:13:00 UTC
Parallelism
93
/100
Blocked
36
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#103,987,920
· 42 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execute
#2
createModule
· blocks 3
#3
execute
#4
createModule
#5
0xb9e20f…a91f
#6
0x67098489
#7
0xaf5e395a
#8
0x0c7abd22
· blocks 2
#10
0x4ccf0801
· blocks 1
#12
0xab083028
#13
0xab083028
#14
main_all
#16
0x6aa460d0
#17
updatePrices
#18
0xb264ae19
#19
0x5acec890
#20
0x5acec890
#21
0x5acec890
#22
0x5acec890
· blocks 1
#23
0x5acec890
#25
0x59558d29
#26
execPerpOps
#27
execPerpOps
#28
0xe3a3c9cc
#29
0x41a8f47c
#30
0x41a8f47c
#31
0x41a8f47c
#32
0x41a8f47c
#33
setData
#34
0x62be7533
#35
execFwdPositionOpsV2
· blocks 2
#39
forward
#9
0x0c7abd22
· blocks 1
#11
0xab083028
· blocks 2
#24
0x59558d29
#37
execFwdPositionOpsV2
· blocks 1
#40
execOrders
· blocks 1
#15
main_all
#36
0x0c7abd22
#38
execFwdPositionOpsV2
#41
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
8
w0
9
w1
10
w0
11
w1
15
w2
22
w0
24
w1
35
w0
36
w2
37
w1
38
w2
40
w1
41
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x2b29a6a1…c868
0x34b655…2a6f
6 touches
3 conflicts
0x044283c3…8a14
0xd32edf…ff58
5 touches
3 conflicts
0xbfb4b02a…4b47
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot
0xaad6be10ae…2c0801
Audit this contract →
← previous block
·
next block →
recent activity