← previous blocknext block →recent activity
Analyzing
Block #100,589,625
55 transactions · 44 stateful · 2026-08-30 22:31:30 UTC
Parallelism
69/100
Blocked
68%
Avg conflicts / tx
1.84
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #100,589,625 · 55 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w16w27w08w09w010w112w218w219w320w421w523w124w525w333w334w136w337w739w441w547w1050w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x676f9f01…a8ac
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x1d9154e7…8821
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
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: Perpl
36 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity