pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,371,156
← previous block
next block →
recent activity
Analyzing
Block #72,371,156
8 transactions · 6 stateful · 2026-05-04 11:54:55 UTC
Parallelism
63
/100
Blocked
33
%
Avg conflicts / tx
0.25
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,371,156
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
0xcf7468f4
#4
updateDataFeedsValuesPartial
#6
setData
#7
0x39435dac
#2
0x0c7abd22
· blocks 1
#5
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffe431af…8faa
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x29021edc…5b89
0x065c9d…c394
3 touches
1 conflict
0x6378537e…8c21
0xd32edf…ff58
3 touches
1 conflict
0x0f779cd8…c0bc
0x065c9d…c394
3 touches
1 conflict
0x964636b3…38ef
0x065c9d…c394
3 touches
1 conflict
0xb8a65e72…5556
0x065c9d…c394
3 touches
1 conflict
0x74e71984…ae90
0x2a68ba…90c5
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:
0x065c9d28…a9c394
1 conflict on slot
0xffe431af56…838faa
Audit this contract →
← previous block
·
next block →
recent activity