pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #71,789,224
10 transactions · 10 stateful · 2026-05-01 19:12:57 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #71,789,224 · 10 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
2w03w15w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00bac013…a28c
0xfd44b3…00d1
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xa8abcc19…3d83
0xea1b8e…c5ec
4 touches
1 conflict
0x92339d95…0800
0x0000a8…8888
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x628927fe…7f2c
0x1efe02…37d6
2 touches
0 conflicts
0x32715c48…0cbc
0xea1b8e…c5ec
2 touches
0 conflicts
0x455b104f…3960
0xea1b8e…c5ec
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: 0xfd44b351…7f00d1
1 conflict on slot 0x00bac0131a…bba28c
Audit this contract →
← previous block·next block →recent activity