← previous blocknext block →recent activity
Analyzing
Block #94,473,491
16 transactions · 16 stateful · 2026-08-09 11:09:16 UTC
Parallelism
69/100
Blocked
56%
Avg conflicts / tx
1.13
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,473,491 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w17w28w39w410w011w112w213w314w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x724cd9ff…6684
0xe4f6e7…9657
8 touches
6 conflicts
0x44ad89ba…cf83
0xe4f6e7…9657
8 touches
6 conflicts
0xc1641f4c…aac2
0x065c9d…c394
8 touches
6 conflicts
0x724cd9ff…6684
0x0cc9b2…7777
8 touches
6 conflicts
0x00000000…0008
0x0ea966…0742
8 touches
6 conflicts
0x0778475b…bd75
0x2a68ba…90c5
8 touches
6 conflicts
0x74f95963…01a2
0x34b655…2a6f
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: USDC (USDC)
10 conflicts on slot 0xa1087a5ca6…0a66c4
Audit this contract →
← previous block·next block →recent activity