pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,879,014
← previous block
next block →
recent activity
Analyzing
Block #100,879,014
7 transactions · 7 stateful · 2026-08-31 22:47:38 UTC
Parallelism
71
/100
Blocked
14
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,879,014
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
multicall
#3
0x59558d29
#5
0x6a960502
#6
setData
#4
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x4f5dc8a7…a5e1
0x065c9d…c394
2 touches
0 conflicts
0xaa5d1ec6…e2af
0x068f22…7908
2 touches
0 conflicts
0xe4053c5c…fccd
0x068f22…7908
2 touches
0 conflicts
0xf91620c4…d3ca
0x068f22…7908
2 touches
0 conflicts
0x0e6850fc…ff99
0x09475a…400f
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity