pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,539,266
← previous block
next block →
recent activity
Analyzing
Block #93,539,266
10 transactions · 10 stateful · 2026-08-06 04:34:58 UTC
Parallelism
80
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,539,266
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39435dac
· blocks 1
#3
0xeb282f7f
#4
executeBatch
#5
0x0f6795d9
· blocks 1
#6
0x3f5c179b
#8
0x6a740f6a
#9
setData
#2
0x39435dac
#7
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeef03d6b…4375
0x34b655…2a6f
4 touches
1 conflict
0x9ba6ae4a…90cb
0x34b655…2a6f
4 touches
1 conflict
0xb13b8081…15ca
0x34b655…2a6f
4 touches
1 conflict
0xb6d30f60…08f6
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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:
Perpl
1 conflict on slot
0xeef03d6b53…734375
Audit this contract →
← previous block
·
next block →
recent activity