pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,681,142
12 transactions · 12 stateful · 2026-05-10 13:21:23 UTC
Parallelism
58/100
Blocked
33%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,681,142 · 12 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0001
0x877f30…7c0b
10 touches
10 conflicts
0x00000000…0003
0x877f30…7c0b
10 touches
10 conflicts
0xe75ca10f…d28a
0x3bd359…433a
10 touches
10 conflicts
0x95e37fef…f5bf
0x3ec731…7777
10 touches
10 conflicts
0x00000000…0000
0x877f30…7c0b
10 touches
10 conflicts
0x68faa0b9…14af
0x368ee5…7ca4
2 touches
0 conflicts
0xcd621226…2df8
0x368ee5…7ca4
2 touches
0 conflicts
0x00000000…000d
0x877f30…7c0b
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: 0x877f3044…087c0b
10 conflicts on slot 0x0000000000…000001
Audit this contract →
← previous block·next block →recent activity