pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,348,832
← previous block
next block →
recent activity
Analyzing
Block #93,348,832
9 transactions · 8 stateful · 2026-08-05 12:37:34 UTC
Parallelism
78
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,348,832
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
· blocks 1
#2
0x5acec890
#3
updateDataFeedsValuesPartial
#5
0x6a732f06
#6
setData
#7
0x59558d29
· blocks 1
#4
batchUpdate
#8
0x59558d29
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x4f5d8f7e…6f56
0x851145…3f07
4 touches
1 conflict
0xe2fccdb2…903c
0x851145…3f07
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0xc660ab51…886f
0x851145…3f07
4 touches
1 conflict
0x7757f5c8…0abb
0x851145…3f07
3 touches
1 conflict
0xccfbd21c…10e3
0x851145…3f07
3 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:
0x80c74517…647210
1 conflict on slot
0x0000000000…00004b
Audit this contract →
← previous block
·
next block →
recent activity