← previous blocknext block →recent activity
Analyzing
Block #74,504,522
10 transactions · 7 stateful · 2026-05-14 08:54:34 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,504,522 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x335a161d…fe7f
0x000000…012a
4 touches
1 conflict
0x2d603f45…1c6f
0x699abc…6a3b
4 touches
1 conflict
0xe0b1fab4…b85c
0x699abc…6a3b
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x50a88d10…679c
0x34b655…2a6f
2 touches
0 conflicts
0x9b8800c1…ed12
0x34b655…2a6f
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: AUSD (AUSD)
1 conflict on slot 0x335a161d76…bdfe7f
Audit this contract →
← previous block·next block →recent activity