← previous blocknext block →recent activity
Analyzing
Block #73,744,002
30 transactions · 26 stateful · 2026-05-10 20:25:25 UTC
Parallelism
87/100
Blocked
62%
Avg conflicts / tx
0.83
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,744,002 · 30 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w16w07w18w09w210w212w013w114w215w316w019w120w123w124w225w127w228w229w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
8 touches
6 conflicts
0x0ac31945…2c72
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0004
0xd5b70d…615b
6 touches
3 conflicts
0x00000000…0000
0x63e48b…53f2
6 touches
3 conflicts
0x00000000…0003
0x63e48b…53f2
6 touches
3 conflicts
0x00000000…0004
0x63e48b…53f2
6 touches
3 conflicts
0x9a555477…19a8
0x754704…b603
6 touches
3 conflicts
0x00000000…0000
0xd5b70d…615b
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: 0xab35264b…1cfa38
6 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity