← previous blocknext block →recent activity
Analyzing
Block #99,134,305
32 transactions · 30 stateful · 2026-08-25 20:09:04 UTC
Parallelism
63/100
Blocked
67%
Avg conflicts / tx
2.13
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #99,134,305 · 32 txs across 12 waves · depth 12
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w27w38w49w510w611w712w813w914w1015w1117w320w225w427w528w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
20 touches
45 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x47b807a2…3307
0x065c9d…c394
10 touches
10 conflicts
0xa366dc41…b2d8
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xe716e1ed…766a
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0019
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: 0xf5b5f7f8…a36d70
45 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity