pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,572,109
← previous block
next block →
recent activity
Analyzing
Block #93,572,109
12 transactions · 11 stateful · 2026-08-06 07:20:04 UTC
Parallelism
83
/100
Blocked
18
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,572,109
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
_makeSwaps
#2
0xab083028
#3
updateDataFeedsValuesPartial
#4
0x0f6795d9
· blocks 2
#5
0x9e76c652
#6
forward
#9
batchUpdate
#10
0xe9316489
#11
setData
#7
0x0f6795d9
#8
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
7
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1bde9f7f…c070
0x34b655…2a6f
4 touches
1 conflict
0x24ca1902…7a87
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x9d9692ac…619b
0x000000…012a
2 touches
0 conflicts
0x11b69a7e…334e
0x01bff4…1071
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
0x1bde9f7fc9…34c070
Audit this contract →
← previous block
·
next block →
recent activity