← previous blocknext block →recent activity
Analyzing
Block #100,601,324
71 transactions · 57 stateful · 2026-08-30 23:30:21 UTC
Parallelism
82/100
Blocked
74%
Avg conflicts / tx
2.69
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #100,601,324 · 71 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w418w319w320w421w522w623w750w958w1161w1062w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
24 touches
66 conflicts
0xca841faa…486a
0x34b655…2a6f
18 touches
36 conflicts
0xbc3526a5…c4ba
0xd32edf…ff58
17 touches
36 conflicts
0x889d5e90…929a
0x2a68ba…90c5
16 touches
28 conflicts
0x00000000…0013
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0015
0x1b6862…e19c
16 touches
28 conflicts
0x872e51c8…ae2b
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…002e
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
66 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity