← previous blocknext block →recent activity
Analyzing
Block #102,548,625
36 transactions · 33 stateful · 2026-09-06 19:12:25 UTC
Parallelism
69/100
Blocked
64%
Avg conflicts / tx
1.83
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #102,548,625 · 36 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w510w412w423w528w631w632w733w834w935w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x5259294b…d82f
0xd32edf…ff58
11 touches
15 conflicts
0x9b4f173c…94e6
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…001d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002d
0x1b6862…e19c
8 touches
6 conflicts
0x91220b8f…7a06
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 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: 0xf5b5f7f8…a36d70
21 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity