← previous blocknext block →recent activity
Analyzing
Block #100,602,260
119 transactions · 63 stateful · 2026-08-30 23:35:03 UTC
Parallelism
83/100
Blocked
70%
Avg conflicts / tx
1.66
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #100,602,260 · 119 txs across 20 waves · depth 20
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
wave w18
wave w19
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w08w010w112w015w118w224w027w159w362w363w464w566w667w769w870w974w477w279w680w782w885w992w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
22 touches
55 conflicts
0xca841faa…486a
0x34b655…2a6f
18 touches
36 conflicts
0x889d5e90…929a
0x2a68ba…90c5
16 touches
28 conflicts
0x955baa36…6e6d
0xd32edf…ff58
13 touches
21 conflicts
0xf3d10975…0d07
0x34b655…2a6f
12 touches
15 conflicts
0xea02471d…1542
0x34b655…2a6f
12 touches
15 conflicts
0x11258774…9892
0x2a68ba…90c5
10 touches
10 conflicts
0x40970e69…da50
0x2b46c0…1669
10 touches
10 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: Perpl
55 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity