pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,210,257
39 transactions · 34 stateful · 2026-05-08 09:03:37 UTC
Parallelism
85/100
Blocked
62%
Avg conflicts / tx
1.13
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #73,210,257 · 39 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w15w06w18w19w211w213w214w015w116w217w318w419w526w129w232w233w334w438w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
12 touches
15 conflicts
0x046a928e…0012
0x2a68ba…90c5
8 touches
6 conflicts
0x7f189cf6…afab
0x065c9d…c394
8 touches
6 conflicts
0xf4730a2d…3538
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xce7bfe5e…5e58
0x065c9d…c394
6 touches
3 conflicts
0x9553af3c…ecde
0x34b655…2a6f
6 touches
3 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
6 touches
3 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: 0xab35264b…1cfa38
15 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity