← previous blocknext block →recent activity
Analyzing
Block #101,975,706
56 transactions · 46 stateful · 2026-09-04 18:48:39 UTC
Parallelism
68/100
Blocked
74%
Avg conflicts / tx
2.57
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #101,975,706 · 56 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
6w07w18w19w210w311w414w627w628w729w830w934w536w748w1049w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
20 touches
45 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0xbde524f4…43bf
0x34b655…2a6f
10 touches
10 conflicts
0x737acb78…fce8
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0xf8f1e808…a4fd
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
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
45 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity