← previous blocknext block →recent activity
Analyzing
Block #73,642,443
16 transactions · 13 stateful · 2026-05-10 09:00:16 UTC
Parallelism
63/100
Blocked
46%
Avg conflicts / tx
0.81
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #73,642,443 · 16 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
1w02w14w05w16w213w314w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf7ec4cb6…8774
0x34b655…2a6f
8 touches
6 conflicts
0xa91c899f…6ee3
0x34b655…2a6f
8 touches
6 conflicts
0x1b9e654e…0a08
0x34b655…2a6f
6 touches
3 conflicts
0x57de3828…3fbb
0x34b655…2a6f
6 touches
3 conflicts
0x5d70606a…1d53
0x34b655…2a6f
6 touches
3 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0x6eba5e7f…4b52
0x34b655…2a6f
6 touches
3 conflicts
0x0711ec2d…d973
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 0xf7ec4cb602…468774
Audit this contract →
← previous block·next block →recent activity