pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,338,161
← previous block
next block →
recent activity
Analyzing
Block #74,338,161
12 transactions · 11 stateful · 2026-05-13 14:27:12 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,338,161
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39ecce49
#2
execute
· blocks 1
#3
updatePrices
#5
0x5bf9264c
#6
0x98717539
#7
0xd2952904
#8
forward
#9
setData
#10
0x39435dac
#11
0x39435dac
#4
0xccf50a51
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0dbf9688…c6cf
0xd18b7e…414b
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x62e20208…be65
0x0555e3…2b9c
2 touches
0 conflicts
0x6677f92f…b7cd
0x0555e3…2b9c
2 touches
0 conflicts
0x846f2172…fd54
0x0555e3…2b9c
2 touches
0 conflicts
0x00000000…0000
0x139aab…382b
2 touches
0 conflicts
0x00000000…0001
0x139aab…382b
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:
0xd18b7ec5…10414b
1 conflict on slot
0x0dbf9688de…b0c6cf
Audit this contract →
← previous block
·
next block →
recent activity