← previous blocknext block →recent activity
Analyzing
Block #100,752,169
98 transactions · 60 stateful · 2026-08-31 12:09:08 UTC
Parallelism
82/100
Blocked
75%
Avg conflicts / tx
2.88
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #100,752,169 · 98 txs across 18 waves · depth 18
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
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w08w09w110w211w312w459w260w361w462w463w568w272w674w775w876w977w1078w1183w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
34 touches
136 conflicts
0xaad6be10…0801
0x2a68ba…90c5
24 touches
66 conflicts
0xca841faa…486a
0x34b655…2a6f
20 touches
45 conflicts
0x26b3a7b0…e7f7
0xd32edf…ff58
17 touches
36 conflicts
0x00000000…0029
0x1b6862…e19c
14 touches
21 conflicts
0x10c19272…7440
0x1b6862…e19c
14 touches
21 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0012
0x1b6862…e19c
14 touches
21 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
136 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity