pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,554,924
← previous block
next block →
recent activity
Analyzing
Block #93,554,924
10 transactions · 10 stateful · 2026-08-06 05:53:41 UTC
Parallelism
60
/100
Blocked
30
%
Avg conflicts / tx
0.3
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,554,924
· 10 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x325dd70c
#2
matchOrders
#3
0xab083028
#4
0x5acec890
· blocks 1
#6
updateDataFeedsValuesPartial
#9
setData
#5
0x5acec890
· blocks 1
#7
0x0f6795d9
· blocks 1
#8
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
7
w2
8
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x317fc387…8bf2
0x0a3323…0a3c
2 touches
0 conflicts
0x0d528651…72f0
0x754704…b603
2 touches
0 conflicts
0x66c70a3f…1e9c
0x754704…b603
2 touches
0 conflicts
0xa060b594…669d
0x754704…b603
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
0xca841faae5…71486a
Audit this contract →
← previous block
·
next block →
recent activity