pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,170,862
14 transactions · 13 stateful · 2026-05-08 04:41:09 UTC
Parallelism
71/100
Blocked
23%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,170,862 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w06w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x8e66da19…66b6
0x065c9d…c394
8 touches
6 conflicts
0x00000000…001a
0x1b6862…e19c
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x2a354a63…0515
0x065c9d…c394
2 touches
0 conflicts
0x3301e294…30a0
0x065c9d…c394
2 touches
0 conflicts
0x7911eea0…aa65
0x065c9d…c394
2 touches
0 conflicts
0x00000000…000d
0x1b6862…e19c
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity