← previous blocknext block →recent activity
Analyzing
Block #73,214,491
16 transactions · 14 stateful · 2026-05-08 09:31:40 UTC
Parallelism
69/100
Blocked
36%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,214,491 · 16 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
5w06w17w28w314w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xef17b8cd…9511
0x34b655…2a6f
8 touches
6 conflicts
0xdaca243a…f9de
0x34b655…2a6f
8 touches
6 conflicts
0xb4441f0b…b692
0x34b655…2a6f
8 touches
6 conflicts
0x21d22421…0b7a
0x34b655…2a6f
6 touches
3 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0x0b2aa636…7087
0x34b655…2a6f
6 touches
3 conflicts
0xc1e986dd…9875
0x34b655…2a6f
6 touches
3 conflicts
0x27132f04…5caa
0x34b655…2a6f
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: Perpl
6 conflicts on slot 0xef17b8cd5c…709511
Audit this contract →
← previous block·next block →recent activity