pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,477,245
16 transactions · 12 stateful · 2026-05-14 05:52:46 UTC
Parallelism
88/100
Blocked
8%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,477,245 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x765c236f…ff45
0x2a68ba…90c5
4 touches
1 conflict
0x45a9aa4d…9d63
0x065c9d…c394
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x5a7fe7ea…c5b6
0x0555e3…2b9c
2 touches
0 conflicts
0x62e20208…be65
0x0555e3…2b9c
2 touches
0 conflicts
0x8e80434a…a96d
0x0555e3…2b9c
2 touches
0 conflicts
0x00000000…0000
0x094452…0a09
2 touches
0 conflicts
0x00000000…0002
0x094452…0a09
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: 0x2a68ba18…8e90c5
1 conflict on slot 0x765c236f2d…b5ff45
Audit this contract →
← previous block·next block →recent activity