← previous blocknext block →recent activity
Analyzing
Block #73,263,012
21 transactions · 20 stateful · 2026-05-08 14:54:23 UTC
Parallelism
71/100
Blocked
45%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #73,263,012 · 21 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
1w03w04w15w26w37w48w514w115w116w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
12 touches
15 conflicts
0x046a928e…0012
0x2a68ba…90c5
8 touches
6 conflicts
0x0b390c61…dc07
0x065c9d…c394
4 touches
1 conflict
0xbd7e37a9…9eb5
0x065c9d…c394
4 touches
1 conflict
0xe4da7ec3…f318
0x065c9d…c394
3 touches
1 conflict
0x31ba6c4c…e2a4
0x065c9d…c394
3 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
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: 0xab35264b…1cfa38
15 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity