← previous blocknext block →recent activity
Analyzing
Block #94,806,789
49 transactions · 48 stateful · 2026-08-10 15:07:08 UTC
Parallelism
92/100
Blocked
13%
Avg conflicts / tx
0.18
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,806,789 · 49 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
1w02w13w24w05w17w145w246w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e76cf03…9cc3
0x34b655…2a6f
6 touches
3 conflicts
0xf807100f…846e
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21c2
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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
3 conflicts on slot 0x5e76cf0367…8a9cc3
Audit this contract →
← previous block·next block →recent activity