pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#71,289,320
← previous block
next block →
recent activity
Analyzing
Block #71,289,320
8 transactions · 7 stateful · 2026-04-29 11:38:53 UTC
Parallelism
50
/100
Blocked
43
%
Avg conflicts / tx
0.38
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,289,320
· 8 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0xb264ae19
· blocks 1
#3
updatePrices
#6
0x69f1ee45
#7
setData
#2
0x20601463
· blocks 1
#4
0x0c7abd22
· blocks 1
#5
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w2
5
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0x84611dd3…b345
0x1b6862…e19c
4 touches
1 conflict
0x6a14a18d…6a59
0x065c9d…c394
4 touches
1 conflict
0x1627b708…d040
0x2a68ba…90c5
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xfe2bac2b…2cec
0x065c9d…c394
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:
0x1b68626d…2de19c
1 conflict on slot
0x0000000000…000015
Audit this contract →
← previous block
·
next block →
recent activity