← previous blocknext block →recent activity
Analyzing
Block #73,642,442
17 transactions · 14 stateful · 2026-05-10 09:00:15 UTC
Parallelism
65/100
Blocked
43%
Avg conflicts / tx
0.65
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #73,642,442 · 17 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
2w07w18w09w110w214w315w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa91c899f…6ee3
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x6eba5e7f…4b52
0x34b655…2a6f
6 touches
3 conflicts
0xf7ec4cb6…8774
0x34b655…2a6f
6 touches
3 conflicts
0x5d70606a…1d53
0x34b655…2a6f
6 touches
3 conflicts
0x13023f15…3eb2
0x34b655…2a6f
6 touches
3 conflicts
0xedb848fe…6534
0x34b655…2a6f
6 touches
3 conflicts
0x8a35acfb…d1a8
0x8d66a4…3095
4 touches
1 conflict
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 0xa91c899f02…fa6ee3
Audit this contract →
← previous block·next block →recent activity